Software defined network-based data processing method, node, and system

ABSTRACT

The present disclosure discloses a software defined network SDN-based data processing system, and the system includes: a source data node, configured to receive a first data packet, and send to a corresponding source control node; the source control node, configured to receive the first data packet, where the first data packet carries a destination address of the first data packet; and determine a destination control node; and the destination control node, configured to receive the first data packet, and generate a second data packet and a matching policy rule. According to a software defined network-based data processing system in an embodiment of the present disclosure, the collaboration capability between nodes is improved so as to reduce the redundancy of multi-node processing in a network device, thereby improving the service processing efficiency of the network. The present disclosure further discloses a software defined network-based data processing method and device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Patent ApplicationNo. PCT/CN2013/079908, filed on Jul. 23, 2013, which claims priority toChinese Patent Application No. 201210564522.5, filed on Dec. 24, 2012,both of which are hereby incorporated by reference in their entireties.

TECHNICAL FIELD

The present disclosure relates to the field of communicationstechnologies, and in particular, to software defined network-based dataprocessing methods, nodes, and systems.

BACKGROUND

Currently, a networking mode of device nodes in a common access networkbasically adopts a distributed autonomic network structure. In thisnetwork structure, each network node is configured separately and worksindependently. Therefore, asymmetric information between network nodesexists, which causes problems such as incapability of sharing servicecapabilities between different network nodes, lack of collaboration, andredundant and repeated execution of service functions, so that theprocessing performance of the whole network is poor. Several scenariosof unreasonable network node capability distribution that are verycommon in network application are described as follows:

1) As shown in FIG. 1, multiple client clusters and server clustersaccess a network through different network nodes, where a client cluster1 accesses the network through a node A, and a server cluster 1 accessesthe network through a node B. An HTTP (Hypertext Transport Protocol)protocol-based IPS (Intrusion Prevention System) service processingcapability is allocated for the network node A; and a service processingcapability of URL (Uniform Resource Locator) filtering is allocated forthe node B. When a network service flow passes the node A and the node Bsequentially, the node A and the node B perform DPI (Deep PacketInspection) identification and parsing processing on the service flow atan application layer due to the need of service processing, therebycausing that different devices execute a part of functions repeatedly onthe same service flow.

2) As shown in FIG. 2, multiple client clusters and server clustersaccess a network through different network nodes, where a client cluster1 accesses the network through a node A, and a server cluster 1 accessesthe network through a node B. A message content-based compressioncapability is allocated for the network node A, but the node B does nothave the decompression capability. When transmission acceleration needsto be performed on a service flow at an application layer the messagemay undergo content compression when passing the source end node A, butcannot be decompressed when passing the destination node B, so that anetwork acceleration service cannot be implemented.

Due to the distributed structure of the existing network and theseparate deployment manner of nodes, service capabilities of networknodes are private and in lack of unified collaboration management, sothat the whole network lacks collaboration for related serviceprocessing at the application layer, the processing is redundant, andthe efficiency is reduced.

How to implement unified resource management on network nodes,reasonably distribute node capabilities and coordinate servicescheduling, and implement multi-node capability sharing and cooperationso as to improve the processing efficiency of the whole network is amajor problem being faced currently.

SUMMARY

Embodiments of the present disclosure provides a software definednetwork (Software Defined Network, SDN)-based data processing system,method, and device, which improves the collaboration capability betweennodes, thereby improving the service processing efficiency of thenetwork.

Embodiments in a first aspect of the present disclosure discloses asoftware defined network-based data processing system, and the systemincludes: a source data node, configured to receive a first data packet,and send the first data packet to a corresponding source control node; asource control node, configured to receive the first data packet sent bythe source data node, where the first data packet carries a destinationaddress of the first data packet, and determine a destination controlnode according to the destination address of the first data packet; andthe destination control node, configured to receive the first datapacket, and generate a second data packet according to the first datapacket and a matching policy rule.

In a possible implementation manner of the embodiments in the firstaspect of the present disclosure, the source data node is specificallyconfigured to receive the first data packet, where the first data packetcarries a source IP address of the first data packet, determine,according to the source IP address of the first data packet or accordingto mapping between a data node and a control node, the source controlnode corresponding to the source data node, and send the first datapacket to the corresponding source control node.

With reference to any of the foregoing embodiments, in a second possibleimplementation manner of the embodiments in the first aspect of thepresent disclosure, the source control node is specifically configuredto receive the first data packet sent by the source data node, where thefirst data packet carries the destination address of the first datapacket, and determine a destination data node according to thedestination address of the first data packet; and if the source controlnode does not manage the destination data node, determine the firstcontrol node managing the source data node and the destination data nodeas the destination control node.

With reference to any of the foregoing embodiments, in a third possibleimplementation manner of the embodiments in the first aspect of thepresent disclosure, the source control node or the source data node isfurther configured to send the first data packet to the destinationcontrol node.

With reference to any of the foregoing embodiments, in a fourth possibleimplementation manner of the embodiments in the first aspect of thepresent disclosure, the matching policy rule includes:mapping/correspondence between sub-tuple information and an actionparameter or a policy parameter, or mapping between application layerinformation and an action parameter or a policy parameter; thedestination control node is specifically configured to: receive thefirst data packet, search the matching policy rule, according tosub-tuple information of the first data packet or application layerinformation of the first data packet, for an action parameter or apolicy parameter corresponding to the sub-tuple information of the firstdata packet or the application layer information of the first datapacket; and generate the second data packet according to the foundaction parameter or policy parameter.

With reference to any of the foregoing embodiments, in a fifth possibleimplementation manner of the embodiments in the first aspect of thepresent disclosure, the data processing system further includes one ormore serving nodes; the matching policy rule includes:mapping/correspondence between sub-tuple information and an actionparameter or a policy parameter, or mapping between application layerinformation and an action parameter or a policy parameter; thedestination control node is specifically configured to: receive thefirst data packet, search the matching policy rule, according tosub-tuple information of the first data packet or application layerinformation of the first data packet, for an action parameter or apolicy parameter corresponding to the sub-tuple information of the firstdata packet or the application layer information of the first datapacket; and send, according to the found action parameter or policyparameter, capability request information to a first serving node havingthe capability of executing the action parameter or policy parameter inthe one or more serving nodes; the first serving node is configured tosend corresponding capability response information to the destinationcontrol node in response to the capability request information; and thedestination control node generates the second data packet according tothe capability response information.

With reference to any of the foregoing embodiments, in a sixth possibleimplementation manner of the embodiments in the first aspect of thepresent disclosure, the destination control node is further configuredto send a second data packet to the source data node, where the seconddata packet carries a destination address of the second data packet; andthe source data node is further configured to send, under management ofthe destination control node, the second data packet to a data nodecorresponding to the destination address of the second data packet.

With reference to any of the foregoing embodiments, in a seventhpossible implementation manner of the embodiments in the first aspect ofthe present disclosure, the data processing system further includes: atleast one relay data node, where the destination control node isconfigured to manage each relay data node; the relay data node stores aflow table corresponding to the relay data node, where the flow table isused to store a processing rule of a data packet; the source data nodestores a flow table corresponding to the source data node, where theflow table is used to store a processing rule of a data packet: thedestination control node is further configured to generate a routingdistribution rule and deliver the routing distribution rule to the relaydata node and the source data node, where the routing distribution ruleis used to allocate a route for the second data packet; the relay datanode is further configured to receive the routing distribution rule sentby the destination control node, and update the flow table of the relaydata node according to the routing distribution rule; the source datanode is further configured to send the second data packet to a relaydata node corresponding to the destination address of the second datapacket according to the updated flow table; and the relay data node isconfigured to send, according to the updated flow table, the second datapacket to a destination data node corresponding to the destinationaddress of the second data packet.

With reference to any of the foregoing embodiments, in an eighthpossible implementation manner of the embodiments in the first aspect ofthe present disclosure, the source data node further stores a flowtable, where the flow table is used to store sub-tuple information of aservice flow data packet and a processing rule corresponding to thesub-tuple information; the destination control node is furtherconfigured to add a control node number field and a service parameterfield in the flow table of the source data node, where, the control nodenumber field is used to represent an index of a destination control nodecorresponding to the source data node, and the service parameter fieldis used to represent an index corresponding to a processing result ofthe sub-tuple information of the service flow data packet.

With reference to the foregoing embodiments, in a ninth possibleimplementation manner of the embodiments in the first aspect of thepresent disclosure, the source data node is further configured toreceive a third data packet, where both the third data packet and thefirst data packet belong to the service flow data packet, and aprocessing rule corresponding to sub-tuple information of the third datapacket is the same as the processing rule corresponding to the sub-tupleinformation of the first data packet.

With reference to the foregoing embodiments, in a tenth possibleimplementation manner of the embodiments in the first aspect of thepresent disclosure, the source data node is further configured todetermine, according to the flow table, a service parametercorresponding to the sub-tuple information from a processing rule recordmatching the sub-tuple information of the third data packet, where theservice parameter is used to represent an index of an action parameteror a policy parameter to be executed for the third data packet; thesource data node carries the service parameter in the third data packetand sends the third data packet to the destination control node; and thedestination control node is further configured to determine, accordingto the service parameter and application layer information of the thirddata packet, the action parameter or policy parameter to be executed forthe third data packet, so as to generate a fourth data packet.

With reference to any of the foregoing embodiments, in an eleventhpossible implementation manner of the embodiments in the first aspect ofthe present disclosure, the destination control node is furtherspecifically configured to add, in the flow table of the source datanode, a control node number field and a service parameter fieldcorresponding to the first data packet, where the control node numberfield is used to represent an index of a destination control nodecorresponding to the source data node, and the service parameter fieldcorresponding to the first data packet is used to represent an index ofa matching policy rule corresponding to sub-tuple information of thefirst data packet, where a service parameter corresponding to the thirddata packet is the index of a matching policy rule of the sub-tupleinformation of the first data packet; the source data node is furtherconfigured to carry the index of the matching policy rule of thesub-tuple information of the first data packet in the third data packetand send the third data packet to the destination control node; and thedestination control node is further configured to determine, accordingto a matching policy rule corresponding to the index of the matchingpolicy rule of the sub-tuple information of the first data packet andapplication layer information of the third data packet, the actionparameter or policy parameter to be executed for the third data packet,so as to generate a fourth data packet.

In the SDN network system according to the embodiment of the presentdisclosure, in a hierarchical deployment manner of control nodes, anextended data node flow table structure, and a capability distributionmethod according to a policy rule, application layer service processingand capability sharing distribution in an SDN network are implemented,so that collaboration between nodes is improved to reduce the redundancyof multi-node processing in a network device, and the problems ofunreasonable node capability distribution, capability dissymmetry, andcapability non-aggregation are solved, thereby improving the serviceprocessing efficiency of the network; at the same time, the hierarchicaldeployment manner of control nodes solves the bottleneck of processingperformance of the control nodes, and maintains the stability,reliability, and scalability of the network.

Embodiments in a second aspect of the present disclosure discloses asoftware defined network-based data processing method, and the methodincludes: receiving, by a source data node, a first data packet;sending, by the source data node, the first data packet to acorresponding source control node, where the first data packet carries adestination address of the first data packet, so that the source controlnode determines a destination control node according to the destinationaddress of the first data packet, and the destination control nodegenerates a second data packet according to the first data packet.

In a first possible implementation manner of the embodiments in thesecond aspect of the present disclosure, the second data packet carriesa destination address of the second data packet, and the method furtherincludes: receiving, by the source data node, the second data packetsent by the destination control node; and sending, by the source controlnode, the second data packet to a data node corresponding to thedestination address of the second data packet.

With reference to any of the foregoing embodiments, in a second possibleimplementation manner of the embodiments in the second aspect of thepresent disclosure, the first data packet carries a source IP address ofthe first data packet, and before the sending, by the source data node,the first data packet to a corresponding source control node, the methodfurther includes: determining the corresponding source control nodeaccording to the source IP address of the first data packet or accordingto mapping between the source data node and a control node.

With reference to any of the foregoing embodiments, in a third possibleimplementation manner of the embodiments in the second aspect of thepresent disclosure, the source data node further stores a flow table,where the flow table is used to store sub-tuple information of a serviceflow data packet and a processing rule corresponding to the sub-tupleinformation; after the source data node sends the first data packet tothe corresponding source control node, the method further includes:receiving, by the source data node, first control information sent bythe destination control node; adding, by the source data node, a controlnode number field and a service parameter field in the flow table of thesource data node according to the first control information, where thecontrol node number field is used to represent an index of a destinationcontrol node corresponding to the source data node, and the serviceparameter field is used to represent an index corresponding to aprocessing result of the sub-tuple information of the service flow datapacket.

With reference to any of the foregoing embodiments, in a fourth possibleimplementation manner of the embodiments in the second aspect of thepresent disclosure, after adding the control node number field and theservice parameter field in the flow table of the source data node, themethod further includes: receiving, by the source data node, a thirddata packet, where both the third data packet and the first data packetbelong to the service flow data packet, and a processing rulecorresponding to sub-tuple information of the third data packet is thesame as the processing rule corresponding to the sub-tuple informationof the first data packet; determining, by the source data node accordingto the flow table, a service parameter corresponding to the sub-tupleinformation from a processing rule record matching the sub-tupleinformation of the third data packet, where the service parameter isused to represent an index of an action parameter or a policy parameterto be executed for the third data packet; carrying, by the source datanode, the service parameter in the third data packet and sending thethird data packet to the destination control node, so that thedestination control node determines, according to the service parameterand application layer information of the third data packet, the actionparameter or policy parameter to be executed for the third data packet,so as to generate a fourth data packet.

According to a software defined network-based data processing methodprovided in the embodiment of the present disclosure, by performing, ona control node, various processing on a data packet received by a datanode, the collaboration capability between nodes is improved and theredundancy of multi-node processing in a network device is reduced aswell; moreover, the capability of the network device to process aservice flow data packet is improved, thereby improving the serviceprocessing efficiency of the network.

Embodiments in a third aspect of the present disclosure discloses asoftware defined network-based data processing method, and the methodincludes: receiving, by a destination control node, a first data packet,where the first data packet carries a destination address of the firstdata packet, the destination control node is determined by a sourcecontrol node according to the destination address of the first datapacket, and the source control node corresponds to a source data nodereceiving the first data packet; generating, by the destination controlnode, a second data packet according to the first data packet and amatching policy rule; and sending the second data packet to the sourcedata node, where the source data node receives the first data packet andcorresponds to the source control node.

In a first possible implementation manner of the embodiments in thethird aspect of the present disclosure, before the receiving, by adestination control node, a first data packet, the method furtherincludes: receiving, by the destination control node, a fifth datapacket sent by the source control node, where the fifth data packetcarries a destination address of the fifth data packet; determining adestination data node according to the destination address of the fifthdata packet; and if the destination control node does not manage thedestination data node, determining a first control node managing thedestination data node and the source data node as a second destinationcontrol node.

With reference to the foregoing embodiment, in a second possibleimplementation manner of the embodiments in the third aspect of thepresent disclosure, the receiving, by the destination control node, afirst data packet specifically includes: receiving, by the destinationcontrol node, the first data packet sent by the source control node orthe source data node.

With reference to any of the foregoing embodiments, in a third possibleimplementation manner of the embodiments in the third aspect of thepresent disclosure, the matching policy rule includes:mapping/correspondence between sub-tuple information and an actionparameter or a policy parameter, or mapping between application layerinformation and an action parameter or a policy parameter; thegenerating, by the destination control node, a second data packetaccording to the first data packet and a matching policy rule includes:searching the matching policy rule, according to sub-tuple informationof the first data packet or application layer information of the firstdata packet, for an action parameter or a policy parameter correspondingto the sub-tuple information of the first data packet or the applicationlayer information of the first data packet; and generating the seconddata packet according to the found action parameter or policy parameter.

With reference to any of the foregoing embodiments, in a fourth possibleimplementation manner of the embodiments in the third aspect of thepresent disclosure, the matching policy rule includes:mapping/correspondence between sub-tuple information and an actionparameter or a policy parameter, or mapping between application layerinformation and an action parameter or a policy parameter; thegenerating, by the destination control node, a second data packetaccording to the first data packet and a matching policy rule includes:searching the matching policy rule, according to sub-tuple informationof the first data packet or application layer information of the firstdata packet, for an action parameter or a policy parameter correspondingto the sub-tuple information of the first data packet or the applicationlayer information of the first data packet; sending, according to thefound action parameter or policy parameter, capability requestinformation to a first serving node having the capability of executingthe action parameter or policy parameter in one or more serving nodes;receiving, by the destination control node, corresponding capabilityresponse information sent by the first serving node in response to thecapability request information; and generating, by the destinationcontrol node, the second data packet according to the capabilityresponse information.

With reference to any of the foregoing embodiments, in a fifth possibleimplementation manner of the embodiments in the third aspect of thepresent disclosure, after the determining, by the source control node, adestination control node according to the destination address of thefirst data packet, the method further includes: sending, by thedestination control node, first control information to the source datanode, where the first control information is used to add a control nodenumber field and a service parameter field in a flow table of the sourcedata node, the control node number field is used to represent an indexof a destination control node corresponding to the source data node, andthe service parameter field is used to represent an index correspondingto a processing result of sub-tuple information of the service flow datapacket.

With reference to any of the foregoing embodiments, in a sixth possibleimplementation manner of the embodiments in the third aspect of thepresent disclosure, after adding a control node number field and aservice parameter field in a flow table of the source data node, themethod further includes: receiving, by the destination control node, athird data packet carrying a service parameter, where both the thirddata packet and the first data packet belong to the service flow datapacket, a processing rule corresponding to sub-tuple information of thethird data packet is the same as the processing rule corresponding tothe sub-tuple information of the first data packet, the serviceparameter is a service parameter corresponding to the sub-tupleinformation, which is determined from a processing rule record matchingthe sub-tuple information of the third data packet, and the serviceparameter is used to represent an index of an action parameter or apolicy parameter to be executed for the third data packet; determining,by the destination control node according to the service parameter andapplication layer information of the third data packet, the actionparameter or policy parameter to be executed for the third data packet,so as to generate a fourth data packet; and sending, by the destinationcontrol node, the fourth data packet to the source data node.

According to a software defined network-based data processing methodprovided in the embodiment of the present disclosure, by performing, ona control node, various processing on a data packet received by a datanode, the collaboration capability between nodes is improved and theredundancy of multi-node processing in a network device is reduced aswell; moreover, the capability of the network device to process aservice flow data packet is improved, thereby improving the serviceprocessing efficiency of the network.

Embodiments in a fourth aspect of the present disclosure discloses adata node for software defined network-based data processing, and thedata node includes: a first receiving module and a first sending module,where the first receiving module is connected to the first sendingmodule; the first receiving module is configured to receive a first datapacket, the first sending module is configured to send the first datapacket received by the first receiving module to a corresponding sourcecontrol node, so that the source control node determines a destinationcontrol node according to a destination address of the first datapacket, and the destination control node generates a second data packetaccording to the first data packet.

In a possible implementation manner of the embodiments in the fourthaspect of the present disclosure, the first receiving module is furtherconfigured to receive the second data packet sent by the destinationcontrol node; the first sending module is further configured to send,according to a destination address of the second data packet carried inthe second data packet, the second data packet received by the receivingmodule to a data node corresponding to the destination address.

With reference to any of the foregoing embodiments, in a second possibleimplementation manner of the embodiments in the fourth aspect of thepresent disclosure, the data node further includes: a storage module,where the storage module is configured to store a flow table, the flowtable is used to store sub-tuple information of a service flow datapacket and a processing rule corresponding to the sub-tuple information;and the first data packet belongs to the service flow data packet.

With reference to any of the foregoing embodiments, in a third possibleimplementation manner of the embodiments in the fourth aspect of thepresent disclosure, the data node further includes: a first processingmodule, where the first processing module is connected to the firstreceiving module; the first receiving module is further configured toreceive first control information sent by the destination control node;the first processing module is configured to add, according to the firstcontrol information, a control node number field and a service parameterfield in the flow table of the storage module, where the control nodenumber field is used to represent an index of a destination control nodecorresponding to the source data node, and the service parameter fieldis used to represent an index corresponding to a processing result ofsub-tuple information of the service flow data packet.

With reference to any of the foregoing embodiments, in a fourth possibleimplementation manner of the embodiments in the fourth aspect of thepresent disclosure, the first processing module is connected to thefirst sending module, the first receiving module is further configuredto receive a third data packet, where both the third data packet and thefirst data packet belong to the service flow data packet, and aprocessing rule corresponding to sub-tuple information of the third datapacket is the same as the processing rule corresponding to the sub-tupleinformation of the first data packet; the first processing moduledetermines, according to the flow table, a service parametercorresponding to the sub-tuple information from a processing rule recordmatching the sub-tuple information of the third data packet, where theservice parameter is used to represent an index of an action parameteror a policy parameter to be executed for the third data packet; and thefirst sending module carries the service parameter in the third datapacket and sends the third data packet to the destination control node,so that the destination control node determines, according to theservice parameter and application layer information of the third datapacket, the action parameter or policy parameter to be executed for thethird data packet, so as to generate a fourth data packet.

According to a data node for software defined network-based dataprocessing, by performing various processing on a data packet receivedby the data node, the collaboration capability between nodes is improvedand the redundancy of multi-node processing in a network device isreduced as well; moreover, the capability of the network device toprocess a service flow data packet is improved, thereby improving theservice processing efficiency of the network.

Embodiments in a fifth aspect of the present disclosure discloses adestination control node for software defined network-based dataprocessing, and the destination control node includes: a secondreceiving module, configured to receive a first data packet, where thefirst data packet carries a destination address of the first datapacket, the destination control node is determined by a source controlnode according to the destination address of the first data packet, andthe source control node corresponds to a source data node receiving thefirst data packet; and a second processing module, configured togenerate a second data packet according to the second data packetreceived by the second receiving module and a matching policy rule.

In a first possible implementation manner of the embodiments in thefifth aspect of the present disclosure, the second receiving module isfurther configured to receive a fifth data packet, where the fifth datapacket carries a destination address of the fifth data packet; thesecond processing module is configured to determine a destination datanode according to the destination address of the fifth data packet; andif the second processing module does not manage the destination datanode, determine a first control node managing the destination data nodeand the source data node as a second destination control node.

With reference to any of the foregoing embodiments, in a second possibleimplementation manner of the embodiments in the fifth aspect of thepresent disclosure, the second receiving module is specificallyconfigured to receive the first data packet sent by the source controlnode or the source data node.

With reference to any of the foregoing embodiments, in a third possibleimplementation manner of the embodiments in the fifth aspect of thepresent disclosure, the matching policy rule includes:mapping/correspondence between sub-tuple information and an actionparameter or a policy parameter, or mapping between application layerinformation and an action parameter or a policy parameter; the secondprocessing module includes: a policy matching unit, configured to searchthe matching policy rule, according to sub-tuple information of thefirst data packet or application layer information of the first datapacket, for an action parameter or a policy parameter corresponding tothe sub-tuple information of the first data packet or the applicationlayer information of the first data packet; and a second data packetgenerating unit, configured to generate the second data packet accordingto the action parameter or policy parameter found by the policy matchingunit.

With reference to any of the foregoing embodiments, in a fourth possibleimplementation manner of the embodiments in the fifth aspect of thepresent disclosure, the matching policy rule includes:mapping/correspondence between sub-tuple information and an actionparameter or a policy parameter, or mapping between application layerinformation and an action parameter or a policy parameter; the secondprocessing module includes: a policy matching unit and a second datapacket generating unit, where the policy matching unit is configured tosearch the matching policy rule, according to sub-tuple information ofthe first data packet or application layer information of the first datapacket, for an action parameter or a policy parameter corresponding tothe sub-tuple information of the first data packet or the applicationlayer information of the first data packet; the second sending module isfurther configured to send, according to the action parameter or policyparameter found by the policy matching unit, capability requestinformation to a first serving node having the capability of executingthe action parameter or policy parameter in one or more serving nodes;the second receiving module is further configured to receivecorresponding capability response information sent by the first servingnode in response to the capability request information; and the seconddata packet generating unit is configured to generate the second datapacket according to the capability response information received by thesecond receiving module.

With reference to any of the foregoing embodiments, in a fifth possibleimplementation manner of the embodiments in the fifth aspect of thepresent disclosure, the second sending module is further configured tosend first control information to a source data node, where the firstcontrol information is used to add a control node number field and aservice parameter field in a flow table of the source data node, thecontrol node number field is used to represent an index of a destinationcontrol node corresponding to the source data node, and the serviceparameter field is used to represent an index corresponding to aprocessing result of sub-tuple information of the service flow datapacket.

With reference to any of the foregoing embodiments, in a sixth possibleimplementation manner of the embodiments in the fifth aspect of thepresent disclosure, the second receiving module is further configured toreceive a third data packet carrying a service parameter, where both thethird data packet and the first data packet belong to the service flowdata packet, a processing rule corresponding to sub-tuple information ofthe third data packet is the same as the processing rule correspondingto the sub-tuple information of the first data packet, the serviceparameter is a service parameter corresponding to the sub-tupleinformation, which is determined from a processing rule record matchingthe sub-tuple information of the third data packet, and the serviceparameter is used to represent an index of an action parameter or apolicy parameter to be executed for the third data packet; the secondprocessing module is further configured to determine, according to theservice parameter and application layer information of the third datapacket, the action parameter or policy parameter to be executed for thethird data packet, and generate a fourth data packet; and the secondsending module is further configured to send the fourth data packet tothe source data node.

According to a control node for software defined network-based dataprocessing provided in the embodiment of the present disclosure, byperforming, on a control node, various processing on a data packetreceived by a data node, the collaboration capability between nodes isimproved and the redundancy of multi-node processing in a network deviceis reduced as well; moreover, the capability of the network device toprocess a service flow data packet is improved, thereby improving theservice processing efficiency of the network.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of the presentdisclosure more clearly, the following briefly introduces theaccompanying drawings required for describing the embodiments of thepresent disclosure. Apparently, the accompanying drawings in thefollowing description show merely some embodiments of the presentdisclosure, and a person of ordinary skill in the art may still deriveother drawings from these accompanying drawings without creativeefforts.

FIG. 1 is a schematic diagram of repeatedly executing identification andparsing functions caused by unreasonable node capability distribution inthe prior art;

FIG. 2 is a schematic diagram of hard implementation of a part ofservices caused by node capability asymmetry in the prior art;

FIG. 3 is a schematic diagram of an SDN network structure and a flowtable format of a data node supporting an openflow OpenFlow protocol;

FIG. 4 is a schematic structural diagram of an SDN network system fordata processing according to an embodiment in a first aspect of thepresent disclosure;

FIG. 5 is an architectural diagram of an SDN network system for dataprocessing according to an embodiment in a first aspect of the presentdisclosure;

FIG. 6 is a flow chart of a method for data processing in an SDN networkaccording to an embodiment in a second aspect of the present disclosure;

FIG. 7 is a flow chart of a method for data processing in an SDN networkaccording to an embodiment in a third aspect of the present disclosure;

FIG. 8 is a flow chart of a device for data processing in an SDN networkaccording to an embodiment in a fourth aspect of the present disclosure;

FIG. 9 is a flow chart of a device for data processing in an SDN networkaccording to an embodiment in a fifth aspect of the present disclosure;

FIG. 10 is a schematic diagram of a specific structure of a flow tableafter a field is added in the flow table according to an embodiment ofthe present disclosure;

FIG. 11 is a schematic diagram of hierarchical management of a controlnode according to an embodiment of the present disclosure;

FIG. 12 is an exemplary diagram of a function implementation manner of adata plane in an SDN data processing system according to an embodimentof the present disclosure;

FIG. 13 is a schematic diagram of implementation of determining an upperlayer control node according to an IP address range according to anembodiment of the present disclosure;

FIG. 14 is a schematic diagram of performing service processing on aservice flow according to an embodiment of the present disclosure;

FIG. 15 is a flow chart of determining a destination control nodeaccording to an embodiment of the present disclosure;

FIG. 16 is a schematic diagram of a data flow direction of an SDNnetwork system according to an embodiment of the present disclosure;

FIG. 17 is a specific implementation scenario of an SDN data processingsystem according to an embodiment of the present disclosure;

FIG. 18 is a second specific implementation scenario of an SDN dataprocessing system according to an embodiment of the present disclosure;

FIG. 19 is a third specific implementation scenario of an SDN dataprocessing system according to an embodiment of the present disclosure;

FIG. 20 is a fourth specific implementation scenario of an SDN dataprocessing system according to an embodiment of the present disclosure;

FIG. 21 is an exemplary diagram of specifically executing rule matchingby a control node in an SDN data processing system according to anembodiment of the present disclosure; and

FIG. 22 is an exemplary diagram of different processing manners for afirst data packet and a third data packet in an SDN data processingsystem according to an embodiment of the present disclosure.

DESCRIPTION OF EMBODIMENTS

The following clearly describes the technical solutions in theembodiments of the present disclosure with reference to the accompanyingdrawings in the embodiments of the present disclosure. Apparently, thedescribed embodiments are merely a part rather than all of theembodiments of the present disclosure. All other embodiments obtained bya person of ordinary skill in the art based on the embodiments of thepresent disclosure without creative efforts shall fall within theprotection scope of the present disclosure.

In order to solve the collaboration problem between network devices, aconcept of software defined network (Software Defined Network, SDN) isproposed. An SDN network includes a data transmission network formed bymany data nodes such as switches and routers, and a control node forperforming unified management and control on all the data nodes, wherethe control node communicates with the data nodes based on an openflowOpenFlow protocol.

The architecture of an SDN network in the industry is shown in FIG. 3,and the SDN network is mainly formed by three layers: a data plane, acontrol plane, and a service plane. The data plane is mainly formed by aswitch or router device supporting the OpenFlow protocol, and on thebasis of basic functions of supporting data exchange and distribution,this device requires possessing 3 elements required by the SDN network:(1) each data node device stores a flow table that can be read andwritten by a control node, where the flow table is formed by flow rules,each flow rule includes a transmission layer attribute of a flow and acorresponding action, and a current OpenFlow device of Type 0 supportsfour simple actions: forwarding, dropping, local processing, and sendingto the control node; (2) the data node and the control node maintain asecure communication link; and (3) support an OpenFlow-basedcommunication protocol interaction procedure. The control plane isformed by a single control node, the control node maintains an OpenFlowprotocol-based communication link with each data node, and the controlnode can read and write a flow table of each data node through theOpenFlow protocol, so as to sense a state of each node, control aforwarding rule of each node, and adjust network routing, bandwidthresource distribution, and the like. In the current SDN networkstructure, the service plane is an abstract layer, and generally refersto a function that can be implemented by the control node, for example,the control node implements, by means of sensing states of the datanodes in the whole network, transmission layer service functions such asdynamic routing distribution, traffic load balancing, network statusmonitoring, and rapid fault location and analyzing.

The following describes a processing procedure of a message in an SDNnetwork by taking a first data packet of a data message as an example,as shown in FIG. 3.

1. A first data packet of a request message of a client enters a datanode A of an SDN network.

2. The node A performs flow table matching on the message to hit adefault rule send to controller, and sends the message to a controlnode.

3. The control node allocates a route for a service flow according to acurrent network state in combination with a certain bandwidth and arouting distribution policy, delivers the rule to a corresponding datanode through an OpenFlow protocol, and adds a rule corresponding to theflow into a flow table of the data node.

4. Then, the control node returns the message to the data node that sentthe message.

5. Each data node forwards the message sequentially according to a flowtable rule.

With reference to FIG. 3, the following describes a flow table format ofthe data node supporting the OpenFlow protocol.

In “openflow-spec-v1.1.0”, as shown in the table at the upper right ofFIG. 3, a defined format is as follows:

InPort: a port for a data packet to enter the data node, for example: acertain network port of a switch device;

VLANID: a label field between Layer 2 and Layer 3 in a TCP/IP protocol,where a source end may be labeled, and a destination end may beprocessed respectively according to different labels;

Ethernet SA: a source end physical address, and a source MAC (MediumAccess Control, medium access control) address;

Ethernet DA: a destination end physical address, and a destination MACaddress;

Ethernet Type: representing a Layer 2 message type of a bearer, forexample, 0x8000 represents an IP message;

IP SA: an IP address of a source end;

IP DA: an IP address of a destination end;

IP Proto: a protocol type of an upper layer bearer of an IP layer, forexample, 0x6 represents bearing a TCP protocol type message;

TCP Src: representing a TCP port of a source end; and

TCP Dst: representing a TCP port of a destination end.

As shown in FIG. 3, (1) for a service flow with a source being a port 6and a VLAN (Virtual Local Area Network, virtual local area network) IDbeing 2002, a flow table matching rule is forwarding to a port 1; (2)for a service flow with a source being the port 1 and a destinationaddress being 1.1.1.1, a flow table matching rule is drop (dropping);(3) for a service flow with a source being the port 6 and acommunication port being 80, a flow table matching rule is local (localprocessing); and (4) for another service flow, a default flow tablematching rule is controller, that is, uploading to a control node.

The concept and device of the SDN network are mainly applied in asmall-scale network that is suitable for centralized management andcontrol, such as a campus network or a lab, and the service plane ismainly aimed at a transmission layer service problem (such as routingcontrol, network traffic balancing, network fault detection and rapiddiagnosis, or dynamic link adjustment), without involving the solutionof processing an application-layer-related service (such as URLfiltering, network application acceleration, IPS defense, messageprotocol classification, or HTTP redirection service). The presentdisclosure is an improved extension method proposed for a limitation ofthe SDN network structure, and on the basis of the SDN network, thepresent disclosure proposes, in a manner of hierarchically deployingmultiple nodes at a control layer, a method for implementingnetwork-wide service capability sharing and application-layer-relatedservice processing.

As shown in FIG. 4, a software defined network-based data processingsystem 40 according to an embodiment of the present disclosure is shown,and the system 40 includes: a source data node 411, configured toreceive a first data packet, and send the first data packet to acorresponding source control node 421; the source control node 421,configured to receive the first data packet sent by the source data node411, where the first data packet carries a destination address of thefirst data packet, and determine a destination control node 422according to the destination address of the first data packet; and thedestination control node 422, configured to receive the first datapacket, and generate a second data packet according to the first datapacket and a matching policy rule.

In an embodiment of the present disclosure, the corresponding sourcecontrol node 421 is determined according to an IP address domain of thesource data node 411 or according to mapping between the source datanode 411 and a control node. A mapping table of a data node and acontrol node may be stored in the source data node 411, and the sourcecontrol node 421 corresponding to the source data node 411 is determinedby looking up the table, and the corresponding source control node 421may also be determined through calculation according to the IP addressdomain of the source data node 411 or a physical topological structure.It can be understood that, the foregoing is only an example for helpingunderstanding of the embodiment of the present disclosure, and cannot beconsidered as a limit to the embodiment of the present disclosure. Thedetermining the source control node according to the source data nodefurther includes another manner that can be implemented by a person ofordinary skill in the art without creative efforts.

In an embodiment of the present disclosure, the source control node 421is specifically configured to receive the first data packet sent by thesource data node 411, where the first data packet carries thedestination address of the first data packet; determine a destinationdata node 413 according to the destination address of the first datapacket; and if the source control node 421 does not manage thedestination data node 413, determine a first control node managing thesource data node 411 and the destination data node 413 as a destinationcontrol node 422.

As shown in FIG. 4, the source control node 421 may be directlyconnected to the destination control node 422, and may also beindirectly connected to the destination control node 422 through anothercontrol node 423 (only one is shown in the drawing, and multiple controlnodes may exist in an actual situation). In another possibleimplementation manner, the source control node 421 also manages thedestination control node 413, and at this time, the source control node421 may be determined as the destination control node 422 (not shown inthe drawing).

In an embodiment of the present disclosure, the source control node 421or the source data node 411 is further configured to send the first datapacket to the destination control node 422.

In an embodiment of the present disclosure, the matching policy ruleincludes: mapping/correspondence between sub-tuple information and anaction parameter or a policy parameter, or mapping between applicationlayer information and an action parameter or a policy parameter; thedestination control node 422 is specifically configured to: receive thefirst data packet, and search the matching policy rule, according tosub-tuple information of the first data packet or application layerinformation of the first data packet, for an action parameter or apolicy parameter corresponding to the sub-tuple information of the firstdata packet or the application layer information of the first datapacket; and generate the second data packet according to the foundaction parameter or policy parameter.

The processing rule refers to a corresponding flow table entry and aprocessing action and a parameter designated in the flow table entry,which are obtained by the data node according to tuple information ofthe data packet and a flow table matching result. After the flow tablematching, a flow table entry of the data node, which includes aprocessing action (send to controller, local, forward . . . ) and aparameter, is obtained.

In an embodiment of the present disclosure, the sub-tuple informationincludes: a source/destination MAC address of the data packet, asource/destination IP address, a source/destination TCP port, a networkport as ingress/egress of the data node (switch), and a VLAN label ofthe data packet, where the information can be obtained from the datapacket.

In an embodiment of the present disclosure, as shown in FIG. 21, 1. anetwork administrator first configures a policy rule set through amanagement plane and delivers the policy rule set to a control node on acontrol plane; for example: the policy rule is, for example, a rule (1)IF tcp.port=80 && url=http://www.xxx.com THEN redirect tohttp://www.yyy.com; and a rule (2) IF tcp.port=8080 && ip.src=10.10.10.*THEN block; and the policy rule set is a set formed by several policyrules; 2. the control node establishes a policy matching tree accordingto the policy rule, for example: a policy matching tree establishedaccording to the foregoing policy rule is shown in FIG. 21, where aninner node in the tree is a condition node, a leaf node is an actionnode, and each edge represents a matched condition; 3. The control nodeextracts tuple information such as tcp/ip/url from the received datapacket, enters the matching tree to start rule matching with a node, andfinally reaches a leaf node to hit a corresponding rule action.

The control node delivers a transmission layer condition (an L4 layercondition) to the data node, such as tcp.port=80 and ip.src=10.10.10.*,and marks for the delivered condition a number such as 0x0001 or 0x0002,that is, a service parameter field of the data node flow table. When thedata node sends the data packet to the control node after performingflow table matching on the data packet to hit a flow table entry, thedata node then adds the service parameter field value in the data packetto be carried to the control node, for example, a service parameter0x0001 is carried to the control node, and then the control nodecorresponds to a hit condition tcp.port=80 according to the number0x0001, so as to directly perform further rule matching from a url nodeof the matching tree, without the need of starting from a root node ofthe matching tree to match the transmission layer of the data packet (L4layer condition) again. It can be understood that, the foregoing exampleis only an example for helping understanding of the embodiment of thepresent disclosure, instead of a limit to a specific solution of theembodiment of the present disclosure, a preset policy rule may be madein another manner, and the control node can also perform further rulematching according to other application layer information listed in theforegoing embodiment.

In the forgoing example, the application layer information may be URLinformation of the data packet, as shown in the following table, and theapplication layer information may be one piece of information shown inthe following table:

DestinationIPAddress Destination IP address InComingPort Source portDestinationPort Destination port InComingVirtualInterface VLAN ID DomainDomain name URL URL information ReqType Request type ContentType Contenttype ServiceType Service type (defined through a string) URLCategory URLcategory ReqSequence Request sequence (request sequence in one PDP)GroupReqSequence URL group request sequence (request in one PDP) CharsetCharacter set Protocol Protocol type UserAgent Terminal type BrowserTypeBrowser type UAProf Terminal type capability e_URL Extended attributeURL e_Charset Extended attribute Character set e_Accept Extendedattribute Accept e_Accept-Charset Extended attribute Accept-Charsete_Accept-Language Extended attribute Accept-Language e_Accept-EncodingExtended attribute Accept-Encoding e_User-Agent Extended attributeUser-Agent e_Profile(x-wap-profile) Extended attributeProfile(x-wap-profile) e_UA-* Extended attribute UA-*(UA-CPU/UA-color//UA-Pixels/etc) e_x-up-devcap-*( Extended attributex-up-devcap-* x-up-devcap-screenpixels/x-up-devcap-iscolor/ etc)e_X-Nokia-*(X-Nokia-MusicShop-Version/ Extended attribute X-Nokia-*X-Nokia-MusicShop-Bearer/etc) e_RedirectType Extended attributeRedirection type e_RedirectDesc Extended attribute Redirectiondescription e_PermitHeader Extended attribute Permit header definitione_ReplaceHeader Extended attribute Replace header definition e_ToolbarExtended attribute Toolbar solution e_Protocol Protocol ID

In an embodiment of the present disclosure, the data processing system40 further includes one or more serving nodes (see FIG. 431, FIG. 432,and FIG. 433); the matching policy rule includes: mapping/correspondencebetween sub-tuple information and an action parameter or a policyparameter, or mapping between application layer information and anaction parameter or a policy parameter; the destination control node 422is specifically configured to: receive the first data packet, search thematching policy rule, according to sub-tuple information of the firstdata packet or application layer information of the first data packet,for an action parameter or a policy parameter corresponding to thesub-tuple information of the first data packet or the application layerinformation of the first data packet; and send, according to the foundaction parameter or policy parameter, capability request information toa first serving node 431 having the capability of executing the actionparameter or policy parameter in the one or more serving nodes; thefirst serving node 431 is configured to send corresponding capabilityresponse information to the destination control node 422 in response tothe capability request information; and the destination control node 422generates the second data packet according to the capability responseinformation.

In an embodiment of the present disclosure, the destination control node422 is further configured to send the second data packet to the sourcedata node 411, where the second data packet carries a destinationaddress of the second data packet; the source data node 411 is furtherconfigured to send, under management of the destination control node422, the second data packet to a data node corresponding to thedestination address of the second data packet.

In an embodiment of the present disclosure, the data processing system40 further includes: at least one relay data node 412 (only one is shownin the drawing, and multiple relay data nodes may exist in an actualsituation), where, the destination control node 422 is configured tomanage each relay data node 412; the relay data node 412 stores a flowtable corresponding to the relay data node 412, where the flow table isused to store a processing rule of a data packet; the source data node411 stores a flow table corresponding to the source data node 411, wherethe flow table is used to store a processing rule of a data packet; thedestination control node 422 is further configured to generate a routingdistribution rule and deliver the routing distribution rule to the relaydata node 412 and the source data node 411, where the routingdistribution rule is used to allocate a route for the second datapacket; the relay data node 412 is further configured to receive therouting distribution rule sent by the destination control node 422, andupdate the flow table of the relay data node 412 according to therouting distribution rule; the source data node 411 is furtherconfigured to send, according to the updated flow table, the second datapacket to the relay data node 412 corresponding to the destinationaddress of the second data packet; and the relay data node 412 isconfigured to send, according to the updated flow table, the second datapacket to the destination data node 413 corresponding to the destinationaddress of the second data packet.

In an embodiment of the present disclosure, the source data node 411further stores a flow table, where the flow table is used to storesub-tuple information of a service flow data packet and a processingrule corresponding to the sub-tuple information; the destination controlnode 422 is further configured to add a control node number field and aservice parameter field in the flow table of the source data node 411,where the control node number field is used to represent an index of adestination control node 422 corresponding to the source data node 411,and the service parameter field is used to represent an indexcorresponding to a processing result of the sub-tuple information of theservice flow data packet.

In an embodiment of the present disclosure, each data node device storesan initial flow table that can be read and written by the control node,the flow table is formed by flow rules, each flow rule includes atransmission layer attribute of a flow and a corresponding action, and acurrent OpenFlow device of Type 0 supports four simple actions:forwarding, dropping, local processing, and sending to a control node.As shown in FIG. 12, the embodiment of the present disclosure implementsfunction supporting on multiple nodes of a control plane by adding acontrol node number Control node and a service parameter Para in theinitial flow table. The control node number Control node and the serviceparameter Para may be added when the source control node modifies a flowtable rule of the data node through an OpenFlow protocol; the controlnode number Control node is designated by the source control node, andrepresents a unique identifier of a corresponding destination controlnode for sending when the data node needs to send a current service flowto a destination control node; the service parameter Para providesrelated information of the service flow for accelerating serviceprocessing of the control node, and is generally matched with acorresponding policy condition or policy action according to thetransmission layer information of the service flow, such as atransmission layer policy condition having been matched with the serviceflow or a rule hit by the service flow. It can be understood that, themodification on the flow table field stored in the data node is only anexample for helping understanding of the embodiment of the presentdisclosure, and cannot be considered as a specific limit to theembodiment of the present disclosure. The adding of the flow table fieldmay be preset on the data node, and may also be completed by a finaldata node. In some situations, only the control node number Control nodemay be added in the flow table of the data node, and the relatedinformation of the service flow provided by the service parameter Paramay be obtained after the control node matches the preset policymatching rule with a service flow data packet A major objective ofadding the service parameter Para is to accelerate the control nodeprocessing the related service flow information, thereby improving theefficiency of network running. An extended OpenFlow flow table structureextends, on the basis of the original flow table, two fields, namely,control node number (Control Node) and service parameter (Para). Thecontrol node number is used to uniquely determine a control node forsending, and the service parameter may be a middle matching result or ahit policy rule of the policy matching. The two fields are added by thecontrol node into the flow table of the data node, the data node, whenhitting the flow rule and sending upstream to a control node, sends apolicy matching parameter to the control node through a TCP-optionsfield, and the control node may accelerate the rule matching accordingto the parameter or execute a corresponding service.

As for a specific data service flow, generally, the first data packet ofthe data service flow matches with a default flow table rule, the datanode sends the first data packet to the control node according to thedefault flow table rule, and the control node performs further rulematching according to the first data packet and then adds a flow tablerule in the flow table of the data node according to a result of therule matching. At this time, the control node extends two fields,namely, the control node number (Control Node) and the service parameter(Para), in the flow table of the data node, so that a subsequent datapacket of the data service flow can match with the two newly addedrules, and is forwarded from the data node according to the new rules.For specific rules, reference may be made to the example in FIG. 21.

In an embodiment of the present disclosure, the source data node isfurther configured to receive a third data packet, where both the thirddata packet and the first data packet belong to the service flow datapacket, and a processing rule corresponding to sub-tuple information ofthe third data packet is the same as the processing rule correspondingto the sub-tuple information of the first data packet.

In an embodiment of the present disclosure, the source data node isfurther configured to determine, according to the flow table, a serviceparameter corresponding to the sub-tuple information from a processingrule record matching the sub-tuple information of the third data packet,where the service parameter is used to represent an index of an actionparameter or a policy parameter to be executed for the third datapacket; the source data node carries the service parameter in the thirddata packet and sends the third data packet to the destination controlnode; and the destination control node is further configured todetermine, according to the service parameter and application layerinformation of the third data packet, the action parameter or policyparameter to be executed for the third data packet, so as to generate afourth data packet.

A specific implementation manner may be shown in FIG. 22, and anoperation for the first data packet matches with a default flow tablerule, which is not described herein again. The third data packet havingthe processing rule of sub-tuple information the same as that of thefirst data packet has a somewhat different processing rule. The thirddata packet may be a data packet from a service flow the same as that ofthe first data packet, and may also be a service flow data packet havingthe same sub-tuple information required during corresponding flow tablematching but having other sub-tuple information that is necessarily thesame. The sub-tuple information is a subset of data packet tupleinformation, for example, the data packet may be formed by a 3-tuple,5-tuple, or 10-tuple, and sub-tuple information may correspondingly havemultiple combinations, for example, only 1 sub-tuple is selected fromthe 3-tuple, or 2 sub-tuples are selected. In an embodiment of thepresent disclosure, the sub-tuple information includes: asource/destination MAC address of the data packet, a source/destinationIP address, a source/destination TCP port, a network port asingress/egress of the data node (switch), and a ULAN label of the datapacket, where the information can be obtained from the data packet. Itcan be understood that, the list of the sub-tuple information and theillustration of the third data packet are only explanations used to helpunderstanding of the embodiment of the present disclosure, and cannot beconsidered as a specific limit to the embodiment of the presentdisclosure.

As shown in FIG. 22 and FIG. 21, the control node delivers to the datanode a transmission layer condition (L4 layer condition, which can beunderstood as a condition matching with the sub-tuple information in aspecific example), such as tcp.port=80 and ip.src=10.10.10.*, and marksfor the delivered condition a number such as 0x0001 and 0x0002, that is,a service parameter field of the data node flow table (which can beunderstood as a result of sub-tuple information matching in a specificexample). After the data node performs flow table matching for the thirddata packet to hit a flow table entry, the data node may directly sendthe third data packet to the destination control node according to aparameter field of the destination control node, without the need offorwarding through the source control node, where the third data packet,when being sent to the destination control node, carries a serviceparameter field value, and the service parameter field valuecorresponding to the third data packet is written into the flow table ofthe source control node when the destination control node performspolicy matching on the first data packet, the third data packet adds theservice parameter field value in the data packet to be carried to thecontrol node, for example, a service parameter 0x0001 is carried to thecontrol node, and the control node corresponds to a hit conditiontcp.port=80 according to the number 0x0001, so as to directly performfurther rule matching from a url node of the matching tree, without theneed of starting from a root node of the matching tree to match thetransmission layer of the data packet (L4 layer condition) again. Inthis manner, a matching operation of the destination control node may beaccelerated, thereby improving the network processing efficiency.

In an embodiment of the present disclosure, the control node and thedata node are connected by using at least two links, where one link is adata link for transmitting a data packet, and the other link is acontrol link for transmitting a control packet. The data node sends thedata packet to the control node through the data link, and the controlnode modifies the flow table field of the data node through the controllink.

The serving node may provide multiple control nodes with unifiedcapabilities of processing an application layer service, such as thefollowing capabilities:

a cache sharing capability: all control nodes may share cacheinformation, and if data requested by one control node can be found inthe cache, the cache data is obtained directly, thereby improving thenetwork access performance;

link quality information sharing: all control nodes may share currentlink status information, and the control node may optimize routingselection according to the link state during routing distribution;

P2P protocol type peer address information sharing, which is capable ofselecting to provide a peer address list in a local area network whenrequesting for a P2P type protocol, thereby improving a P2P typedownloading speed; and

network acceleration service message compression and decompressioncapability.

The various service processing capabilities are provided, in an openOpenAPI interface manner, to the control node for calling, and thevarious capabilities can be deployed in a multi-thread, multi-process,or multi-device manner; the same capability can share data through asharing pool, the capability sharing pool may be in a form of a globalvariable, shared memory, or unified resource access device, and thecontrol node may process the first data packet by calling thecapabilities of the serving node, so as to generate the processed seconddata packet.

In the SDN network system 40 according to the embodiment in the firstaspect of the present disclosure, in a hierarchical deployment manner ofcontrol nodes, an extended data node flow table structure, and acapability distribution method according to a policy rule, applicationlayer service processing and capability sharing distribution in an SDNnetwork are implemented, so that collaboration between nodes is improvedto reduce the redundancy of multi-node processing in a network device,and the problems of unreasonable node capability distribution,capability dissymmetry, and capability non-aggregation are solved,thereby improving the service processing efficiency of the network; atthe same time, the hierarchical deployment manner of control nodessolves the bottleneck of processing performance of the control nodes,and maintains the stability, reliability and scalability of the network.

With reference to FIG. 5, the following describes an SDN network system50 for data processing according to an embodiment in the first aspect ofthe present disclosure. As shown in FIG. 5, the SDN network system 50includes: a data plane 51, where the data plane 51 includes at least twodata nodes, and a data node receiving a service flow data packet is asource data node; a control plane 52, where the control plane 52includes at least one control node, the control node is configured tomanage the data nodes of the data plane according to a preset rule, anda source control node Cnode1 manages a source data node 511; the sourcedata node 511 sends first request information to the source control nodeCnode1, where the first request information includes a first data packetreceived by the source data node 511, and the first data packet includesa destination address of the first data packet; the source control nodeCnode1 determines a destination control node 522 according to thedestination address of the first data packet; the destination controlnode 522 generates a second data packet according to the first datapacket and a preset policy rule; and the source data node 511 receivesthe second data packet sent by the destination control node 522, andsends the second data packet under management of the destination controlnode 522.

In an embodiment of the present disclosure, the control node isconfigured to manage the data nodes of the data plane according to thepreset rule, including: group the data nodes of the data plane 51, so asto obtain at least two grouped data nodes; the control node adopts ahierarchical management manner, where a bottom layer control nodemanages one group of the grouped data nodes; an upper layer control nodemanages at least one of bottom layer control nodes, that is to say, theupper layer control node manages at least one group of the grouped datanodes; and a top layer control node manages all data nodes of the dataplane 51.

In an embodiment of the present disclosure, as shown in FIG. 11, thedata plane includes multiple edge data nodes (a relay data node is notshown) and is divided into several areas in symmetric sectors. In FIG.11, an area A and an area B are marked, the control plane is formed bymultiple layers of control nodes, the control nodes node1 and node2respectively manage edge data nodes and relay data nodes (not shown inthe drawing) in the area A and the area B, a parent node node11 of thecontrol nodes node1 and node2 manages all nodes in the area A and thearea B, and likewise, the control nodes adopt a hierarchical manner, sothat the parent node can manage all areas managed by all sub-nodes, andthe uppermost layer control node can manage all data nodes of the dataplane.

In an embodiment of the present disclosure, the source control nodeCnode1 determining the destination control node 522 according to thedestination address of the data packet includes: determining thedestination data node 512 according to the destination address of thefirst data packet; and if the source control node Cnode1 manages thedestination data node 512, determining the source control node Cnode1 asthe destination control node 522. It can be understood that, for ease ofdescription, this embodiment is not shown in FIG. 5.

In an embodiment of the present disclosure, if the source control nodeCnode1 does not manage the destination data node 512, a second controlnode managing the source data node 511 and the destination data node 512at the same time is determined as the destination control node 522.

In an embodiment of the present disclosure, the destination control node522 generating a second data packet according to the first data packetand a matching policy rule includes: performing, by the destinationcontrol node 522, policy rule matching on the first data packetaccording to the matching policy rule, so as to obtain a result afterthe policy matching; and if the destination control node 522 can executethe result after the policy matching, generating, by the destinationcontrol node 522, the second data packet according to the result afterthe policy matching. The matching policy rule may be a correspondingaction or parameter to be executed by the destination control node forthe data packet, and may also be processing performed by the destinationcontrol node on the data packet according to a requirement of anapplication layer service.

In an embodiment of the present disclosure, the network system 50further includes: a service plane 53, where the service plane 53 isconfigured to provide a service processing capability for the controlplane 52; if the destination control node 522 cannot execute the resultafter the policy matching, the destination control node 522 sends,according to the result after the policy matching, capability requestinformation to the service plane 53; the service plane 53 sendscorresponding capability response information to the destination controlnode 522 in response to the capability request information; and thedestination control node 522 generates the second data packet accordingto the capability response information. The service plane 53 may provideunified capabilities of processing an application layer service formultiple control nodes, the capabilities can correspondingly execute theresult after the policy matching of the data packet, various serviceprocessing capabilities are provided, in an open interface mannerOpenAPI for application programs, to the control node for calling, andthe various capabilities can be deployed in a multi-thread,multi-process, or multi-device manner; the same capability can sharedata through a sharing pool, and the capability sharing pool may be in aform of a global variable, shared memory, or unified resource accessdevice.

In an embodiment of the present disclosure, the network system 50further includes: a management plane 54, where the management plane 54is configured to manage at least one of a network topology of the dataplane 51, a policy rule of the control plane 52, and the serviceprocessing capacity of the service plane 53. The network topologymanagement includes a communication path between data plane nodes, portdistribution, and an IP address section range of a client accessed byeach data node. The policy rule management refers to a rule related toservice processing that is configured by a user, and the policy rule isformed by a transmission layer or application layer policy condition anda corresponding service processing action. The management plane mayimplement the foregoing management manner during initial setting of theSDN network system, and may also perform setting or modification on theforegoing management manner according to a real-time situation of theSDN network or a user requirement when the SDN network system runs.

In the SDN network system 50 according to the embodiment in the secondaspect of the present disclosure, in a hierarchical deployment manner ofcontrol nodes, an extended data node flow table structure, and acapability distribution method according to a policy rule, applicationlayer service processing and capability sharing distribution in an SDNnetwork are implemented, so that collaboration between nodes is improvedto reduce the redundancy of multi-node processing in a network device,and the problems of unreasonable node capability distribution,capability dissymmetry, and capability non-aggregation are solved,thereby improving the service processing efficiency of the network; atthe same time, the hierarchical deployment manner of control nodessolves the bottleneck of processing performance of the control nodes,and maintains the stability, reliability and scalability of the network.

With reference to FIG. 6, the following describes a software definednetwork-based data processing method according to an embodiment in thesecond aspect of the present disclosure.

As shown in FIG. 6, the method includes:

S61: A source data node receives a first data packet.

S62: The source data node sends the first data packet to a correspondingsource control node, where the first data packet carries a destinationaddress of the first data packet, so that the source control nodedetermines a destination control node according to the destinationaddress of the first data packet, and the destination control nodegenerates a second data packet according to the first data packet.

S63: The source data node receives the second data packet sent by thedestination control node.

According to a software defined network (SDN)-based data processingmethod provided in the embodiment in the second aspect of the presentdisclosure, by performing, on a control node, various processing on adata packet received by a data node, the collaboration capabilitybetween nodes is improved and the redundancy of multi-node processing ina network device is reduced as well; moreover, the capability of thenetwork device to process a service flow data packet is improved,thereby improving the service processing efficiency of the network.

With reference to FIG. 7, the following describes a software definednetwork-based data processing method according to an embodiment in athird aspect of the present disclosure.

As shown in FIG. 7, the method includes:

S71: A destination control node receives a first data packet, where thefirst data packet carries a destination address of the first datapacket, and the destination control node is determined by a sourcecontrol node according to a destination address of the first datapacket.

S72: The destination control node generates a second data packetaccording to the first data packet and a matching policy rule.

S73: Send the second data packet to a source data node.

According to a software defined network (SDN)-based data processingmethod provided in the embodiment in the third aspect of the presentdisclosure, by performing, on a control node, various processing on adata packet received by a data node, the collaboration capabilitybetween nodes is improved and the redundancy of multi-node processing ina network device is reduced as well; moreover, the capability of thenetwork device to process a service flow data packet is improved,thereby improving the service processing efficiency of the network.

With reference to FIG. 8, the following describes a software definednetwork-based data node 10 according to an embodiment in a fourth aspectof the present disclosure. The data node 10 includes: a first receivingmodule 101 and a first sending module 102, where the first receivingmodule 101 is connected to the first sending module 102. The firstreceiving module 101 is configured to receive a first data packet, andthe first sending module 102 is configured to send the first data packetreceived by the first receiving module 101 to a corresponding sourcecontrol node, so that the source control node determines a destinationcontrol node according to a destination address of the first datapacket, and the destination control node generates a second data packetaccording to the first data packet; and the first receiving module 101is further configured to receive the second data packet sent by thedestination control node.

According to a software defined network (SDN)-based data node 10provided in an embodiment in the fourth aspect of the presentdisclosure, the collaboration capability between nodes is improved andthe redundancy of multi-node processing in a network device is reducedas well; moreover, the capability of the network device to process aservice flow data packet is improved, thereby improving the serviceprocessing efficiency of the network.

The data node 10 is in communication connection to an external device ora control node, so as to receive and process a data flow sent by theexternal device or the control node, and is configured to send relateddata information to the external device or the control node.

In an embodiment of the present disclosure, the data node 10 furtherincludes: a flow table 103, where the flow table is used to store tupleinformation of a data packet and a processing rule corresponding to thetuple information. The sub-tuple information includes: asource/destination MAC address of the data packet, a source/destinationIP address, a source/destination TCP port, a network port asingress/egress of the data node (switch), and a ULAN label of the datapacket, where the information can be obtained from the data packet.

The flow table is formed by flow rules, each flow rule includes atransmission layer attribute of a flow and a corresponding action, and acurrent openflow OpenFlow device of Type 0 supports four simple actions:forwarding, dropping, local processing, and sending to a control node.

In an embodiment of the present disclosure, if the first data packetsatisfies the preset processing rule, the first sending module 102 sendsfirst request information to the source control node.

In an embodiment of the present disclosure, the data node 10 furtherincludes a first processing module 104, where the first processingmodule 104 is configured to obtain a destination control node accordingto the destination control node information received by the firstreceiving module 101; and

the first processing module 104 is further configured to add a controlnode number field and a service parameter field in a flow table 103according to the destination control node information, where the controlnode number field is used to represent a destination control nodecorresponding to the source data node, and the service parameter fieldis used to represent a result of a processing rule performed by thesource data node on a data packet.

In an embodiment of the present disclosure, as shown in FIG. 12, theembodiment of the present disclosure implements function supporting ofmultiple nodes on the control plane by adding a control node numberControl node and a service parameter Para in an initial flow table. Thecontrol node number Control node and the service parameter Para may beadded when the source control node modifies a flow table rule of thedata node through an OpenFlow protocol; the control node number Controlnode is designated by the source control node, and represents a uniqueidentifier of a corresponding destination control node for sending whenthe data node requires sending the current service flow to a destinationcontrol node; the service parameter Para provides related information ofthe service flow for accelerating service processing of the controlnode, and is generally matched with a corresponding policy condition orpolicy action according to the transmission layer information of theservice flow, such as a transmission layer policy condition having beenmatched with the service flow or a rule hit by the service flow. It canbe understood that, the modification on the flow table field stored inthe data node is only an example for helping understanding of theembodiment of the present disclosure, and cannot be considered as aspecific limit to the embodiment of the present disclosure. The addingof the flow table field may be preset on the data node, and may also becompleted by a final data node. In some situations, only the controlnode number Control node may be added in the flow table of the datanode, and the related information of the service flow provided by theservice parameter Para may be obtained by the control node according tothe preset policy matching rule and after service flow data packetmatching. The major objective of adding the service parameter Para is toaccelerate the control node processing the related service flowinformation, thereby improving the efficiency of network running.

In an embodiment of the present disclosure, the adding the control nodenumber field and the service parameter field in the flow table 103includes that: the processing module 104 performs rule matchingprocessing on the received data packet according to the flow table 103,and fills a result after the rule matching processing into the flowtable 103; and the first sending module 102 sends the result after therule matching processing of the data packet to the destination controlnode through the service parameter field of the flow table 103.

In an embodiment of the present disclosure, the control node number isused to uniquely determine a control node for sending, and the serviceparameter may be a middle matching result or a hit policy rule of thepolicy matching. The two fields are added by the control node into theflow table of the data node, the data node, when hitting the flow ruleand sending to the control node, sends a policy matching parameter tothe control node through a TCP-options field, and the destinationcontrol node may accelerate the rule matching according to the parameteror execute a corresponding service.

With reference to FIG. 9, the following describes a destination controlnode 11 for software defined network-based data processing provided inan embodiment in the fifth aspect of the present disclosure. Thedestination control node 11 includes: a second receiving module 111,where the second receiving module 111 is configured to receive a firstdata packet, the first data packet carries a destination address of thefirst data packet, and the destination control node is determined by asource control node according to the destination address of the firstdata packet;

a second processing module 113, configured to generate a second datapacket according to the second data packet received by the secondreceiving module 111 and a matching policy rule; and

a second sending module 112, configured to send the second data packetgenerated by the second processing module 113 to a source data node,where the source data node receives the first data packet, andcorresponds to the source control node.

The second processing module 113 may be a processor or another devicehaving a data processing capability.

According to a destination control node 11 for software defined network(SDN)-based data processing provided in an embodiment in the fifthaspect of the present disclosure, the collaboration capability betweennodes is improved and the redundancy of multi-node processing in anetwork device is reduced as well; moreover, the capability of thenetwork device to process a service flow data packet is improved,thereby improving the service processing efficiency of the network.

The destination control node 11 is in communication connection to thedata node or the source control node. In an embodiment of the presentdisclosure, the destination control node 11 is also in communicationconnection to a serving node. The destination control node 11 isconfigured to receive and process a data flow sent by the data node, thesource control node, and the serving node, and is configured to sendrelated data information to the data node, the source control node, andthe serving node.

In an embodiment of the present disclosure, the destination control node11 further includes a second sending module 112, where the secondsending module 112 is configured to send the second data packetgenerated by the processing module 113 to the source data node.

In an embodiment of the present disclosure, the destination control node11 further includes a management module 114, where the management module114 is configured to manage the source data node to send the second datapacket.

In an embodiment of the present disclosure, the second sending module112 is further configured to send response information to the sourcedata node, where the response information is used to add a control nodenumber field and a service parameter field in a flow table of the sourcedata node, the control node number field is used to represent adestination control node corresponding to the source data node, and theservice parameter field is used to represent a result of a processingrule performed by the source data node on a data packet.

In an embodiment of the present disclosure, the processing module 113generating a second data packet according to the first data packet and apreset policy rule includes that: the processing module 113 performspolicy rule matching on the first data packet according to the presetpolicy rule, so as to obtain a result after the policy matching; and ifthe processing module 113 can execute the result after the policymatching, the processing module 113 generates the second data packetaccording to a result after the policy matching. If the processingmodule 113 cannot execute the result after the policy matching, thesecond sending module 112 sends, according to a result after the policymatching executed by the processing module 113, capability requestinformation to a serving node; and the processing module 113 generatesthe second data packet according to capability response informationreceived by the second receiving module 111 from the serving node, wherethe capability response information is generated by the serving node inresponse to the corresponding capability request information.

The following describes the foregoing data processing method, node, andsystem in an SDN-based network system through specific implementationdetails. It should be noted that, for ease of illustration, someimplementation manners used in the system may also be applied in themethod or device, and some implementation manners used in the method mayalso be applied in the system or device. It can be understood that, thefollowing implementation manner is only a specific example for helpingunderstanding of the present disclosure, instead of a limit to thetechnical solution of the embodiment of the present disclosure, and thetechnical solution of the embodiment of the present disclosure furtherincludes another manner that can be implemented by a person of ordinaryskill in the art without creative efforts.

With reference to FIG. 5, the following describes a structure andfunctions of an SDN system for data processing according to anembodiment of the present disclosure.

As shown in FIG. 5, the SDN system for data processing, from theperspective of function division, includes four function planes: a dataplane, a control plane, a service plane, and a management plane; andfrom the perspective of service data processing, includes three layers:a data layer, a control layer, and a service layer in sequence frombottom to top.

(1) The data plane is formed by data switch nodes, and a data node iscompatible with existing SDN network node functions, and can supportcommunication with a control node based on an OpenFlow protocol. Thedata plane is responsible for implementing a forwarding processingfunction of a service flow according to a flow table delivered by thecontrol plane.

The data nodes of the data plane can be classified into two categories:an edge data node, which is a node connected to an external device andallows the external device to access a network, where this type of nodeis mainly responsible for performing data interaction with the externaldevice, and both the foregoing source data node and the destination datanode belong to the edge data node; and a relay data node, which is anode only connected to another internal data node, where the relay datanode is only connected to a relay data node or an edge data node in theSDN network, is not in direct communication connection to the externaldevice to generate data interaction, but is in indirect communicationconnection to the external device through the edge data node.

In an embodiment of the present disclosure, each data node device storesan initial flow table that can be read and written by the control node,the flow table is formed by flow rules, each flow rule includes atransmission layer attribute of a flow and a corresponding action, and acurrent OpenFlow device of Type 0 supports four simple actions:forwarding, dropping, local processing, and sending to the control node.As shown in FIG. 12, the embodiment of the present disclosure implementsfunction supporting on multiple nodes of a control plane by adding acontrol node number Control node and a service parameter Para in theinitial flow table. The control node number Control node and the serviceparameter Para may be added when the source control node modifies a flowtable rule of the data node through an OpenFlow protocol; the controlnode number Control node is designated by the source control node, andrepresents a unique identifier of a corresponding destination controlnode for sending when the data node requires sending the current serviceflow to a destination control node; the service parameter Para providesrelated information of the service flow for accelerating serviceprocessing of the control node, and is generally matched with acorresponding policy condition or policy action according to thetransmission layer information of the service flow, such as atransmission layer policy condition having been matched with the serviceflow or a rule hit by the service flow. It can be understood that, themodification on the flow table field stored in the data node is only anexample for helping understanding of the embodiment of the presentdisclosure, and cannot be considered as a specific limit to theembodiment of the present disclosure. The adding of the flow table fieldmay be preset on the data node, and may also be completed by a finaldata node. In some situations, only the control node number Control nodemay be added in the flow table of the data node, and the relatedinformation of service flow provided by the service parameter Para maybe obtained by the control node according to the preset policy matchingrule and after service flow data packet matching. The major objective ofadding the service parameter Para is accelerating the control nodeprocessing the related service flow information, thereby improving theefficiency of network running.

With reference to FIG. 12, the following describes a specificimplementation manner of functions of a data plane according to anembodiment of the present disclosure. As shown in FIG. 12, because onedata node may be in communication with multiple control nodes on thecontrol plane, the data node needs to specify a unique identifier ofsending to a control node, when a flow table action is send tocontroller, that is, sending to a control node. Therefore, as shown inFIG. 10, an extended OpenFlow flow table structure extends, on the basisof the original flow table, two fields, namely, a control node number(Control Node) field and a service parameter (Para) field. The controlnode number is used to uniquely determine a control node for sending,and the service parameter may be a middle matching result or a hitpolicy rule of policy matching. The two fields are added by the controlnode into the flow table of the data node, the data node, when hittingthe flow rule and sending to the control node, sends a policy matchingparameter to the control node through a TCP-options field, and thecontrol node may accelerate the rule matching according to the parameteror execute a corresponding service.

A source control node for uploading, which is preset by the data node 2for a service flow from an IP address range 1.1.*.* is a control node 1.

For a service flow entering from a port 6, if a ULAN ID thereof is 2002,a default matching rule of the data node 2 is forwarding the serviceflow to a port1, at this time, processing of an application layerservice is not involved, and a processing action corresponding to thematching rule can be implemented on the data node 2.

For a service flow entering from the port 1, if an IP address thereof is2.2.2.2, the default matching rule of the data node 2 is dropping a datapacket of the service flow, at this time, the processing of anapplication layer service is not involved either, and the processingaction corresponding to the matching rule can be implemented on the datanode 2.

For a service flow entering from a port 6, if a communication portthereof is 80, the default matching rule of the data node 2 is sending adata packet of the service flow to a control node, a number of thecorresponding control node is 1, that is, sending the data packet to thecontrol node 1, and a value of the service parameter Para is 10, thatis, hitting a policy rule corresponding to 10, for example, the policyrule may be as follows:

IF port=80 && url=www.xxx.com THEN redirect to url=www.yyy.com

where the condition of port=80 corresponds to the service parameter 10.

For another service flow, a matching rule of the data node 2 is sendinga data packet of the service flow to a control node, a number of thecorresponding control node is 1, that is, sending the data packet to thecontrol node 1, and a value of the service parameter Para is 0, that is,hitting a policy rule corresponding to 0, for example, the policy rulemay be, for example, a rule as follows:

IF url=www.xxx.com THEN redirect to url=www.zzz.com.

The policy rule is configured by a network administrator through rulemanagement of a management plane, the control node delivers, accordingto a condition of whether the rule specifically involves a transmissionlayer or an application layer (an IF part of the policy rule), a flowtable parameter to the data node. For example, in the examplecorresponding to the service parameter 10, the information about thedata node being only matched with the data packet port 80 can be sent tothe control node through the service parameter 10, the control nodelearns, according to the service parameter, that the data node has beenmatched with the data packet satisfaction condition port=80, so thecontrol node only needs to continuously match to check whether a urlsatisfies a condition of url=www.xxx.com, without the need of furthermatching a port number of the data packet. This example differs from theexample where the value of the service parameter is 0 that, the controlnode distinguishes, according to the service parameters 0 and 10,whether the condition of port=80 is matched.

It can be understood that, the foregoing embodiment is only an examplefor helping understanding of the embodiment of the present disclosure,and cannot be considered as a specific limit to the embodiment of thepresent disclosure. The embodiment of the present disclosure may furtherinclude another manner that can be implemented by a person of ordinaryskill in the art without creative efforts.

(2) In addition to being compatible with the existing transmission layerservice functions of the SDN network, such as traffic control, routingdistribution, and load balancing, the control plane is also responsiblefor implementing application layer services, such as protocolidentification and parsing, policy rule matching, and sending an actionto the data node according to a rule matching result and calling acorresponding service function.

In the present disclosure, the control plane adopts a manner ofhierarchically deploying multiple nodes, and according to a location ofthe data node and IP address information of a service flow, classifies aservice flow managed by each control node by area and flow. Moreover, aprinciple that one service flow is always managed by the same controlnode is satisfied.

In an embodiment of the present disclosure, the control plane dividesareas of the data plane in symmetric sectors, and each control node canmanage an edge data node and all relay data nodes in one symmetric area.A method of managing control nodes by area is shown in FIG. 11. The dataplane includes multiple edge data nodes (a relay data node is not shown)and is divided into several areas in symmetric sectors. In FIG. 14, anarea A and an area B are marked, the control plane is formed by multiplelayers of control nodes, the control nodes node1 and node2 respectivelymanage edge data nodes and relay data nodes in the area A and the areaB, a parent node node11 of the control nodes node1 and node2 manages allnodes in the area A and the area B, and likewise, the control nodesadopt the hierarchical manner, so that the parent node can manage allareas managed by all sub-nodes, and the uppermost layer control node canmanage all data nodes of the data plane.

The specific procedure of determining a control node for managing aservice flow is shown in FIG. 15. When receiving the service flow sentby a data node for the first time, the control node determines,according to a destination IP address of the service flow and a routingselection result, areas where data nodes of the data plane for theservice flow to enter the network and exit the network are located. If alocation of the data node for the service to exit the network and thatof the data node for the service flow to enter the network are not in amanagement area of the current control node, the control node sends theservice flow to an upper layer control node for processing, andaccordingly, the service flow is finally determined to be managed by acertain control node according to the areas where the nodes for enteringand leaving the network are located.

The method for dividing control nodes according to the IP address of theservice flow allows one data node to be managed by multiple controlnodes at the same time, and the data node may select a correspondingcontrol node according to an IP address range of the service flow.

In an embodiment of the present disclosure, as shown in FIG. 13, thedata node selects the corresponding control node according to the IPaddress range of the service flow in the following manner

The control plane is formed by multiple control nodes, the control nodedivides the controlled data nodes according to symmetric sector areas,the control nodes node1 and node2 control the data nodes in the range ofthe area A at the same time, and the data nodes distribute service flowsto different control nodes according to a source IP, where a serviceflow having an IP ranging from 1.1.1.1 to 1.1.1.127 corresponds to acontrol node number 1 (corresponding to the control node node1) in theflow table, and a service flow having an IP ranging from 1.1.1.128 to1.1.1.254 corresponds to a control node number 2 (corresponding to thecontrol node node2) in the flow table. The control node numberscorresponding to the data nodes in terms of different IP address rangesmay be preset in the flow table of the data nodes. It can be understoodthat, the foregoing embodiment is only an example for understanding theembodiment of the present disclosure, and cannot be considered as aspecific limit to the embodiment of the present disclosure. As shown inFIG. 15, an upper layer control node may also be determined according todifferent IP address ranges, where for a service flow having an IPranging from 1.1.1.1 to 1.1.1.127, an upper layer control node thereofis a node11, and a service flow having an IP ranging from 1.1.1.128 to1.1.1.254 corresponds to an upper layer control node node22.

(3) A service plane may provide unified capabilities of processing anapplication layer service for multiple control nodes, such as thefollowing capabilities:

a cache sharing capability: all control nodes may share cacheinformation, and if data requested by one control node can be found inthe cache, the cache data is obtained directly, thereby improving thenetwork access performance;

link quality information sharing: all control nodes may share currentlink status information, and the control node may optimize routingselection according to the link state during routing distribution;

P2P protocol type peer address information sharing, which is capable ofselecting to provide a peer address list in a local area network whenrequesting for a P2P type protocol, thereby improving a P2P typedownloading speed; and

network acceleration service message compression and decompressioncapability.

Various service processing capabilities are provided, in an open OpenAPIinterface manner, to the control node for calling, and the variouscapabilities can be deployed in a multi-thread, multi-process, ormulti-device manner; the same capability can share data through asharing pool, and the capability sharing pool may be in a form of aglobal variable, shared memory, or unified resource access device.

In an embodiment of the present disclosure, the capability executionprocedure of the service plane includes that: the control node registersa certain capability with the service plane according to ruleconfiguration, the service plane copies the capability for the controlnode, and at the same time, the control node specifies a capabilityexecution point in the service processing procedure; and when thecontrol node is matched with a certain service processing action, thecapability execution point in a processing link is activated to call,through an open interface, the service processing capability of theservice plane.

In an embodiment of the present disclosure, the capability executionprocedure of the service plane includes: (1) initialization registrationstage, where the control node is started, according to a universal setof service rules currently on the control node, for example, cachesharing is configured on the current control node, the control nodefirst performs capability registration with the service plane, theservice plane, after receiving a capability registration request of thecontrol node, distributes corresponding resources to the control node,for example, distributes data storage space and performs aninitialization operation on information of the currently registerednode, and at the same time, the control node specifies a capabilityexecution point in an internal processing procedure, for example,distributes a capability scheduling point at an action execution stageafter hitting a rule. (2) Capability activation at the running stage,when the control node needs to schedule a certain capability of theservice layer at the capability scheduling point during a procedure ofexecuting service processing, the control node initiates a capabilityexecution request to the service plane, for example, the control nodesinitiates a request for caching information to the service plane in acache capability sharing service, the service plane, after receiving theexecution request of the control node, searches a sharing cache poolaccording to an index of the cache content requested by the controlnode, returns cache data to the control node if the cache data is found,and marks as finding a cache, and if the service plane does not find thecache data in the sharing cache pool, returns null, and marks as notfinding the cache data, and the control node continues the serviceprocessing according to a returned result of the capability execution ofthe service plane. (3) Exit to cancel registration stage, the controlnode needs to cancel registration with the service plane when exitingthrough normal closing, the control node initiates a registrationcancellation request message to the service plane, the service planewithdraws the distributed resources according to the request message ofthe control node, for example, withdraws the distributed space, andexecutes an operation of clearing registration information of thecontrol node.

It can be understood that, the foregoing capability execution procedureof the service plane is only a specific example for helpingunderstanding of the embodiment of the present disclosure, instead of aspecific limit to the embodiment of the present disclosure. Multipleprocessing capabilities and service manners can be set for the serviceplane in advance, without the need of registering with the service planeby the control node. The embodiment of the service plane capabilitiesmay further include another manner that can be implemented by a personof ordinary skill in the art without creative efforts.

(4) A management plane is responsible for data plane network topologystructure management, policy rule management, and service plane resourcemanagement. The network topology management includes a communicationpath between data plane nodes, port distribution, and an IP addresssection range of a client accessed by each data node. The policy rulemanagement refers to a rule related to service processing that isconfigured by a user, and the policy rule is formed by a transmissionlayer or application layer policy condition and a corresponding serviceprocessing action. The management plane may implement the foregoingmanagement manner during initial setting of the SDN network system, andmay also perform setting or modification on the foregoing managementmanner according to a real-time situation of the SDN network or a userrequirement when the SDN network system runs.

In an embodiment of the present disclosure, the management plane isresponsible for data plane network structure management, data node andcontrol node connection topology management, policy rule management, andservice plane resource management. The management plane is aconfiguration management interface provided for a network administrator.At an initial stage of system booting, the network administratordelivers topology information to every control node through themanagement plane, so as to provide link connection information forsubsequent routing distribution of the control node. The policy ruleinformation is formed by multiple rules, each policy rule is formed byL1-4 layers or an application layer condition and a correspondingservice action, for example, rule 1: IF (condition)IP=10.10.10.* andurl=www.abcd.com/* service flow, THEN (action) redirecturl=www.xxxx.com/portal executes a redirection action, whereIP=10.10.10.* is a condition forming transmission layer information, andurl is a condition forming L7 layer information; the management planeprovides a rule configuration interface for the network administrator,the network administrator configures a policy rule set and delivers therule set to the control node through the management plane, and thecontrol node completes initialization according to the distributed ruleset, including registering capability with the service plane.

As shown in FIG. 14, in an embodiment of the present disclosure,capabilities of the data node and the control node are distributed bymeans of centralized management of policy rules of the management planeand according to the configuration policy rule of the user, andspecifically, six service processing points are divided according to arequest or response type of the service flow and locations for theservice flow to enter and exit the network: {circle around (1)} a datanode where a request message enters the network; {circle around (2)} acontrol node which the request message enters; {circle around (3)} adata node where the request message exits the network; {circle around(4)} a data node where a response message enters the network, {circlearound (5)} a control node which the response message enters; and{circle around (6)} a data node where the response message exits thenetwork. The service processing points are distributed and acorresponding capability is allocated for the node according to acondition type and an action type of the policy rule, and thedistribution method is shown in the drawing. From the physicalperspective, {circle around (1)} and {circle around (6)} correspond tothe same physical data node, {circle around (2)} and {circle around (5)}correspond to the same physical control node, and {circle around (3)}and {circle around (4)} corresponding to the same physical data node.

Example 1: the policy condition is a condition depending on transmissionlayer message information, and the policy action is a non-service actionsuch as dropping or forwarding, so that a transmission layer conditioncorresponding to the data node needs to be allocated at the locations{circle around (1)} and {circle around (4)} to serve as a tuple of anOpenFlow flow table, where an action of the flow table is the policyaction (forwarding or dropping).

Example 2: the policy condition is a condition depending on transmissionlayer information of a request message, and the policy action is acertain type of service processing, so that a transmission layercondition corresponding to the data node needs to be allocated at thelocation {circle around (1)} to serve as a tuple of an OpenFlow flowtable, where an action of the flow table is send to controller, that is,sending to a control node, Control Node is a number of a control node atthe location {circle around (2)}, a policy parameter is an index of acorresponding service action, and at the same time, a service processingcapability corresponding to the control node policy action needs to beallocated at the location {circle around (2)}. The control node may bedirectly indexed, according to the policy parameter of the message sentby the data node, to corresponding service processing that needs to beexecuted.

Example 3: the policy condition is a condition depending on transmissionlayer and application layer information of a request message, and thepolicy action is a certain type of service processing, so that atransmission layer condition corresponding to the data node needs to beallocated at the location {circle around (4)} to serve as a tuple of anOpenFlow flow table, where an action of the flow table is sendtocontroller, that is, sending to a control node, Control Node is a numberof a control node at the location {circle around (5)}, a policyparameter is a middle result of policy matching of the transmissionlayer information, and at the same time, Layer 7 protocol identificationand parsing, rule matching, and a corresponding service processingcapability of the control node need to be allocated at the location{circle around (5)}. The control node obtains, according to the policyparameter of the message sent by the data node, the middle result oftransmission layer condition matching of the message, completes thepolicy matching in combination with the message information obtainedthrough application layer processing, and executes corresponding serviceprocessing according to a result of the policy matching.

With reference to FIG. 16, the following describes a data flow of an SDNsystem for data processing according to an embodiment of the presentdisclosure.

As shown in FIG. 16, in an SDN network system for data processingaccording to an embodiment of the present disclosure,

after a source data node receives a service flow data packet, the sourcedata node first performs flow table matching of a transmission layer onthe data packet, and executes a corresponding action according to a hitrule. If the hit matching rule is sending to a control node, execute 1.

The source data node 1 sends data information to a source control node1, where the data information includes a first data packet of theservice flow received by the source data node. The source control node 1determines a destination control node 2 according to a destination IPaddress of the first data packet of the service flow.

The destination control node 2 modifies a flow table rule of the sourcedata node through an OpenFlow protocol according to the data informationsent by the source data node 1, and adds a control node number and aservice parameter field. The control node number is a unique mark of acorresponding control node for sending when the current service flowneeds to be sent to a control node. The service parameter field isdelivered by the destination control node 2 to the source data node 1,so as to mark a policy rule index corresponding to a flow table entry inthe source data node.

The source data node 1 performs rule matching on the data packetaccording to the flow table rule, is finally matched with a flow tablerule R, and performs forwarding, local processing, or sending to acontrol node according to an action parameter in the flow table rule R,where if the action is sending to a control node, a control node forsending is selected according to a number of the control node forsending in the flow table rule R, and the service parameter field in theflow table rule R is filled in an extended field of the data packet, forexample, the service parameter is carried to the control node through aTCP-options field, the service parameter field is written by thedestination control node 2 into the flow table of the data node 1, andthe control node may accelerate the service rule matching procedurethrough the service parameter carried in the data packet.

An initial control node 1 sends the received data packet of the serviceflow to a final data node 2 for the final data node 2 to process, andthe service parameter field is added to the TCP-options field of theextended field along with the data packet to be carried to thedestination control node 2.

The service plane can provide unified capabilities of processing anapplication layer service for the destination control node 2, variousservice processing capabilities can be provided, in an open OpenAPIinterface manner, for calling by the destination control node 2, and thedestination control node 2 sends request information to the serviceplane according to the data packet received from the source control node1, so as to request calling the service capability required forprocessing the data packet.

The service plane sends the service capability called by the destinationcontrol node 2 to the destination control node 2, and the destinationcontrol node 2 performs processing on the data packet of the serviceflow by using the service capability, so as to obtain the processedservice flow data packet.

The destination control node 2 sends the processed service flow datapacket to the source data node 1, and at the same time, the destinationcontrol node 2 allocates a route for the service flow according to acurrent network state and in combination with a certain bandwidth and arouting distribution policy, and delivers the rule to a correspondingrelay data node through an OpenFlow protocol, so as to add the rulecorresponding to the flow in a flow table of the relay data node.

The source data node 1 sends the service flow data packet processed bythe destination control node 2 to a destination data node 3 through oneor more relay data nodes 2.

It can be understood that, the foregoing embodiment is only a specificexample for helping understanding of the embodiment of the presentdisclosure, and cannot be considered as a limit to the embodiment of thepresent disclosure, the foregoing data numbers of 1-8 cannot beconsidered as a limit to the sequence of the steps of data flowdirection transmission, where a part of the steps may have exchangedorders, or may be executed in another manner that can be implemented bya person of ordinary skill in the art without creative efforts.

With reference to FIG. 17 to FIG. 20, the following describes severalspecific implementation scenarios of an embodiment of the presentdisclosure.

As shown in FIG. 17, a data message of a certain service flow in aclient cluster 1 enters an SDN network from a data node A, and the datamessage is transmitted through multiple relay data nodes (not shown inthe drawing), and reaches a server cluster 1 through a data node B.

Both the data node A and the data node B are managed by a control nodeCnode1, and the control node Cnode1 maintains flow tables of the datanode A and the data node B through an OpenFlow protocol. (1) A serviceflow data packet sent by a client first passes the data node A; (2) whena first data packet (first packet) of the service flow reaches the datanode A, the data node A obtains, by performing flow table matching onthe first data packet, an action corresponding to a default flow tableentry, that is, send to controller, a default control node numberCnode1, and a default service parameter being null; (3) the data node Asends the data packet to the default control node Cnode1 according tothe control node number, and the control node Cnode1 performs policyrule matching on the data packet. Assuming that a network administratorconfigures a policy rule 1: IF ip=11.11.11.* && protocol=HTTP THEN IPScheck; a rule 2: IF ip=11.11.11.* && url=www.xxx.com THEN block; aresult of the policy matching of the data packet is satisfying a number10 condition of ip=11.11.11.*, the control node Cnode1 delivers anadditional flow table entry I to the data node A, where a content of theflow table entry I is a service parameter 10 corresponding to a dataflow having ip=11.11.11.* in a tuple, and it is determined according toa destination address of the data packet that a data node for the datapacket to exit the network is B; because both the data node A and thedata node B are managed by the control node Cnode1, the control nodeCnode1 is determined as a destination control node, and a control nodenumber delivered by the control node A to the data node flow table entryI is a node number of the control node; (4) the control node Cnode1updates flow tables of various relay data nodes on a data flow route andthe data node B through the OpenFlow protocol; (5) the control nodeCnode1 forwards the data packet to a data node, so that each data nodeperforms matching and forwarding on the data packet according to a flowtable rule of the data node, and finally, the first data packet exitsthe network through the data node B to reach the server; and (6) thedata node processes a subsequent data packet on the service flowaccording to the flow table rule.

The sharing capability pool of the service plane contains a data packetidentification and parsing function aimed at an HTTP (hypertexttransport protocol, Hypertext Transport Protocol) protocol, and a URL(Uniform Resource Locator, uniform resource locator) matchingcapability.

The control node Cnode1 registers a service processing capability withthe service plane on the basis of a preset matching rule, and when it isrequired to match a certain service processing action, the control nodeCnode1 may activate the service processing capability of the serviceplane through an open interface. If protocol identification and parsingor URL matching processing need to be performed on the service flow, thecontrol node Cnode1 calls the service processing capability of theservice plane to process the service flow, and send the processed datapacket to the data node A.

In the foregoing example, (7) when the control node Cnode1 performspolicy matching on the subsequent message of the service flow, if aservice parameter carried in a data packet sent by the data node is 10,that is, ip=11.11.11.* is satisfied, the control node Cnode1 needs tofurther perform matching on the data packet to check whether a conditionurl=www.xxx.com and a condition protocol=HTTP are satisfied, and thecontrol node Cnode1 first activates the protocol identification andparsing function to the service plane; (8) the service plane, whenreceiving a capability request of the control node, performsidentification and parsing processing on the packet, and returns aresult to the control node; (9) the control node determines that if theidentification and parsing result is protocol=HTTP, a URL matchingcapability is further activated, the service plane continues to completethe URL matching on the data packet and returns a result to the controlnode; (10) the control node completes the policy matching according tothe result returned by the service plane, and executes a response policyaction, for example, if an execution action block block of a rule 2 ismatched, the control node updates a flow table entry of the data node,and sets an action corresponding to the service flow in the data node Aas block. It can be understood that, the foregoing embodiment is only anexample for helping understanding of the embodiment of the presentdisclosure, instead of a specific limit to the embodiment of the presentdisclosure.

As shown in FIG. 18, a data massage of a certain service flow in aclient cluster 1 enters an SDN network from a data node A, the datamessage is transmitted through multiple relay data nodes (not shown inthe drawing), and reaches a server cluster 2 through a data node C. Boththe data node A and the data node C are managed by a node Cnode2, andthe data node A and the data node C are in communication connection withthe node Cnode2 through an OpenFlow protocol.

Like the foregoing example, the data node A performs flow table matchingon a first packet of a service flow (assuming that a source IP is11.11.11.11), hits a default flow table entry, and sends the firstpacket to the control node Cnode 2; the control node Cnode 2 performspolicy rule matching on the first data packet to determine a data node Cfor the data packet to exit the network, determines the control nodeCnode2 as a destination control node, and updates a flow table of a datanode which the data plane service flow needs to pass. Assuming that apolicy rule configured by a network administrator is: IF ip=11.11.11.*THEN block; the control node determines, according to a path of the datanode and control node of the SDN network through which the messageflows, {circle around (1)} the data node A where a request messageenters the network; {circle around (2)} the control node Cnode2 whichthe request message enters; {circle around (3)} the data node C wherethe request message exits the network; {circle around (4)} the data nodeC where a response message enters the network, {circle around (5)} thecontrol node Cnode2 which the response message enters; and {circlearound (6)} the data node A where the response message exits thenetwork; the control node adds, according to the rule, a flow tableentry I having a tuple being ip=11.11.11.* and an action being block tothe data node A; in processing of a subsequent service flow data packet,when the flow table matching performed by the data node A on the datapacket hits the flow table entry I, the data node A directly drops thedata packet, and matches with the hit policy rule at an ingress of thedata packet the first time, so as to avoid data transmission andprocessing of a subsequent node, thereby reducing the network bandwidthresources of the subsequent node device, and avoiding unnecessaryconsumption of processing resources on the subsequent node.

It can be understood that, the data message of the service flow may alsobe in a form of client-client, server-client, or server-server; the datanode A and the data node C may be managed by different nodes, and acontrol node is determined according to the foregoing manner, the formof the communication connection between the data node A and the datanode C and the nodes is not limited to the OpenFlow protocol only, butfurther includes a communication connection manner that can be adoptedby a person of ordinary skill in the art without creative efforts; andthe data node A and the data node C may also be in direct communicationconnection without using a relay data node. If the service flow of thedata node A has multiple destination addresses, a drop operation is onlyexecuted on the data node A or a subsequent relay node for a networkrouting path having a flow table rule of a destination address beingdrop, which does not affect transmission of another network routingpath, and the network routing path and bandwidth resource distributionare managed by the control node. It can be understood that, theforegoing is only an example for helping understanding of the technicalsolution of the embodiment of the present disclosure, instead of a limitto the embodiment of the present disclosure. The technical solution ofthe embodiment of the present disclosure may further include anothersolution that can be implemented by a person of ordinary skill in theart without creative efforts.

As shown in FIG. 19, a data message of a certain service flow in aclient cluster 1 enters an SDN network from a data node A, the datamessage is transmitted through multiple relay data nodes (not shown inthe drawing), and reaches a server through a data node B. The data nodeA is managed by a node Cnode1, and the data node A is in communicationconnection with the node Cnode1 through an OpenFlow protocol; the datanode B is managed by a node Cnode3, and the data node B is incommunication connection with the node Cnode3 through the OpenFlowprotocol. A control node CnodeA is determined according to the nodeCnode1 and the node Cnode3, where a procedure of determining the controlnode has been described in the foregoing, and is not described hereinagain.

When application layer transmission acceleration needs to be performedon a network service flow, the data node A does not need to be given thecapability of compressing service flow message information. The datanode A, after rule matching, uploads the service flow messageinformation to the control node CnodeA, and the control node CnodeAobtains, according to a capability requirement of the service flow, acorresponding compression capability and decompression capability basedon message content from a service plane, where the obtaining, by thecontrol node CnodeA, the foregoing capabilities from the service planemay be implemented by calling through an open interface. The compressionon the service flow data message is completed on the control nodeCnodeA, and the compressed service flow data message is transmitted tothe data node A. The data node A transmits the compressed service flowdata message to a data node B, and the data node B then uploads theservice flow data message to the control node CnodeA for decompression,so as to obtain the decompressed service flow data message. Accordingly,the service flow of the foregoing client cluster 1 can implementacceleration of application layer transmission from the data node A tothe data node B. It can be understood that, the foregoing embodiment isonly an example for helping understanding of the embodiment of thepresent disclosure, instead of a limited explanation to the technicalsolution of the present disclosure.

As shown in FIG. 20, in an SDN network structure, a service planecontains a sharing capability pool, the same capability may share datathrough the sharing capability pool, and the sharing capability pool maybe in a form of a global variable, a shared memory, or the same resourceaccess device.

A client in a client cluster 1 and a client in a client cluster 2request the same streaming media content, and a service flow of theclient in the client cluster 1 accesses the SDN network system through adata node A. The data node A is managed by a node Cnode1, and a datanode D is managed by a node Cnode2.

First, a related procedure of determining a destination control nodeCnode1 of the data node A and a destination control node Cnode 2 of thedata node D is described in the foregoing, and is not described hereinagain. Both the control nodes Cnode1 and Cnode 2 register a Cache cachecapability with a service plane, and at the same time, the service planeallocates a read and write interface of Cache cache data for the controlnodes Cnode1 and Cnode 2; (1) a data flow of the data node A cachesstreaming media data content when passing through the control nodeCnode1; (2) the data node D accesses the streaming media data contentthe same as that of the data node A, and when an access request datapacket reaches the control node Cnode 2 through the data node D, thecontrol node Cnode 2 activates a Cache cache capability to the serviceplane, and searches for cache data through a cache data read interface,because the control node Cnode1 has cached the data content requested bythe data node A, the control node Cnode 2 finds the cached streamingmedia content, encapsulates the data into a response data packet to bereturned to the data node D. The procedure of the data node D acquiringthe data from the server again is saved, thereby increasing the responsespeed of the client, and reducing the processing pressure of the serverat the same time. It can be understood that, the foregoing is only anexample for helping understanding of the technical solution of theembodiment of the present disclosure, and cannot be considered as alimit to the technical solution of the embodiment of the presentdisclosure. The control node may also enable the data node D to obtaincorresponding streaming media content by establishing communicationconnection of the data node A and the data node D, or in another mannerthat can be implemented by a person of ordinary skill without creativeefforts.

It can be clearly learned by a person skilled in the art that, toachieve the purpose of convenient and brief description, for a detailedworking process of the foregoing apparatus, reference may be made to thecorresponding process in the foregoing method embodiment, and thedetails are not described herein again.

In the several embodiments provided in the present application, itshould be understood that the disclosed system, apparatus, and methodmay be implemented in other manners. For example, the describedapparatus embodiment is merely exemplary. For example, the unit divisionis merely logical function division and may be other division in actualimplementation. For example, multiple units or components may becombined or integrated into another system, or some features may beignored or not performed. In addition, the displayed or discussed mutualcouplings or direct couplings or communication connections may beimplemented through some interfaces. The indirect couplings orcommunication connections between the apparatuses or units may beimplemented in electronic, mechanical, or other forms.

In addition, functional units in the embodiments of the presentdisclosure may be integrated into one processing unit, or each of theunits may exist alone physically, or two or more units may be integratedinto one unit.

When the functions are implemented in a form of a software functionalunit and sold or used as an independent product, the functions may bestored in a computer-readable storage medium. Based on such anunderstanding, the technical solutions of the present disclosureessentially, or the part contributing to the prior art, or a part of thetechnical solutions may be implemented in a form of a software product.The computer software product is stored in a storage medium, andincludes several instructions for instructing a computer device (whichmay be a personal computer, a server, or a network device) to performall or a part of the steps of the methods described in the embodiment ofthe present disclosure. The foregoing storage medium includes: anymediums that can store program code, such as a USB flash drive, aremovable hard disk, a read-only memory (Read-Only Memory, ROM), arandom access memory (Random Access Memory, RAM), a magnetic disk, or anoptical disc.

The foregoing descriptions are merely exemplary embodiments of thepresent disclosure, but are not intended to limit the protection scopeof the present disclosure. Any variation or replacement readily figuredout by a person skilled in the art within the technical scope disclosedin the present disclosure shall fall within the protection scope of thepresent disclosure. Therefore, the protection scope of the presentdisclosure shall be subject to the protection scope of the claims.

What is claimed is:
 1. A software defined network-based data processingsystem, comprising: a source data node, configured to receive a firstdata packet, and send the first data packet to a corresponding sourcecontrol node, wherein the first data packet includes a destinationaddress of the first data packet; the source control node, configured toreceive the first data packet sent by the source data node, anddetermine a destination control node according to the destinationaddress of the first data packet; and the destination control node,configured to receive the first data packet, and generate a second datapacket according to the first data packet and a matching policy rule. 2.The data processing system according to claim 1, wherein, the sourcedata node is configured to receive the first data packet, wherein thefirst data packet includes a source IP address of the first data packet,and wherein the source data node is further configured to determine thesource control node corresponding to the source data node according tothe source IP address of the first data packet or according to mappingbetween a data node and a control node, and send the first data packetto the corresponding source control node.
 3. The data processing systemaccording to claim 1, wherein, the source control node is configured toreceive the first data packet sent by the source data node, wherein thefirst data packet carries the destination address of the first datapacket, and wherein the source data node is further configured todetermine a destination data node according to the destination addressof the first data packet; and if the source control node does not managethe destination data node, determine a first control node managing thesource data node and the destination data node as the destinationcontrol node.
 4. The data processing system according to claim 1,wherein, the source control node or the source data node is furtherconfigured to send the first data packet to the destination controlnode.
 5. The data processing system according to claim 1, wherein, thematching policy rule comprises: mapping/correspondence between sub-tupleinformation and an action parameter or a policy parameter, or mappingbetween application layer information and an action parameter or apolicy parameter; and the destination control node is configured to:receive the first data packet, and search the matching policy rule,according to sub-tuple information of the first data packet orapplication layer information of the first data packet, for an actionparameter or a policy parameter corresponding to the sub-tupleinformation of the first data packet or the application layerinformation of the first data packet; and generate the second datapacket according to the found action parameter or policy parameter. 6.The data processing system according to claim 1, wherein, the dataprocessing system further comprises one or more serving nodes; thematching policy rule comprises: mapping/correspondence between sub-tupleinformation and an action parameter or a policy parameter, or mappingbetween application layer information and an action parameter or apolicy parameter; the destination control node is configured to: receivethe first data packet, search the matching policy rule, according tosub-tuple information of the first data packet or application layerinformation of the first data packet, for an action parameter or apolicy parameter corresponding to the sub-tuple information of the firstdata packet or the application layer information of the first datapacket; and send, according to the found action parameter or policyparameter, capability request information to a first serving node havingthe capability of executing the action parameter or policy parameter inthe one or more serving nodes; the first serving node is configured tosend corresponding capability response information to the destinationcontrol node in response to the capability request information; and thedestination control node is further configured to generate the seconddata packet according to the capability response information.
 7. Thedata processing system according to claim 1, wherein, the destinationcontrol node is further configured to send the second data packet to thesource data node, wherein the second data packet carries a destinationaddress of the second data packet; and the source data node is furtherconfigured to send, under management of the destination control node,the second data packet to a data node corresponding to the destinationaddress of the second data packet.
 8. The data processing systemaccording to claim 7, wherein, the data processing system furthercomprises: at least one relay data node, wherein the destination controlnode is configured to manage each relay data node; the relay data nodestores a flow table corresponding to the relay data node, wherein theflow table is used to store a processing rule of a data packet; thesource data node stores a flow table corresponding to the source datanode, wherein the flow table is used to store a processing rule of adata packet; the destination control node is further configured togenerate a routing distribution rule and deliver the routingdistribution rule to the relay data node and the source data node,wherein the routing distribution rule is used to allocate a route forthe second data packet; the relay data node is further configured toreceive the routing distribution rule sent by the destination controlnode, and update the flow table of the relay data node according to therouting distribution rule; the source data node is further configuredto: send, according to the updated flow table, the second data packet toa relay data node corresponding to the destination address of the seconddata packet; and the relay data node is configured to: send, accordingto the updated flow table, the second data packet to a destination datanode corresponding to the destination address of the second data packet.9. The data processing system according to claim 1, wherein, the sourcedata node further stores a flow table, wherein the flow table is used tostore sub-tuple information of a service flow data packet and aprocessing rule corresponding to the sub-tuple information; and thedestination control node is further configured to add a control nodenumber field and a service parameter field in the flow table of thesource data node, wherein, the control node number field is used torepresent an index of a destination control node corresponding to thesource data node, and the service parameter field represents an indexcorresponding to a processing result of the sub-tuple information of theservice flow data packet.
 10. The data processing system according toclaim 9, wherein, the source data node is further configured to receivea third data packet, wherein, both the third data packet and the firstdata packet belong to the service flow data packet, and a processingrule corresponding to sub-tuple information of the third data packet isthe same as the processing rule corresponding to the sub-tupleinformation of the first data packet.
 11. The data processing systemaccording to claim 10, wherein, the source data node is furtherconfigured to determine, according to the flow table, a serviceparameter corresponding to the sub-tuple information from a processingrule record matching the sub-tuple information of the third data packet,wherein the service parameter represents an index of an action parameteror a policy parameter to be executed for the third data packet; thesource data node is further configured to carry the service parameter inthe third data packet and send the third data packet to the destinationcontrol node; and the destination control node is further configured todetermine, according to the service parameter and application layerinformation of the third data packet, the action parameter or policyparameter executed for the third data packet, so as to generate a fourthdata packet.
 12. The data processing system according to claim 9,wherein, the destination control node is further configured to add, inthe flow table of the source data node, a control node number field anda service parameter field corresponding to the first data packet,wherein, the control node number field represents an index of adestination control node corresponding to the source data node, and theservice parameter field corresponding to the first data packet is usedto represent an index of a matching policy rule corresponding to thesub-tuple information of the first data packet, wherein, a serviceparameter corresponding to the third data packet is the index of thematching policy rule corresponding to the sub-tuple information of thefirst data packet; and the source data node is further configured tocarry the index of the matching policy rule corresponding to thesub-tuple information of the first data packet in the third data packetand send the third data packet to the destination control node, thedestination control node is further configured to determine, accordingto a matching policy rule corresponding to the index of the matchingpolicy rule of the sub-tuple information of the first data packet andthe application layer information of the third data packet, an actionparameter or a policy parameter executed for the third data packet, soas to generate a fourth data packet.
 13. A software definednetwork-based data processing method, comprising: receiving, by a sourcedata node, a first data packet, wherein the first data packet includes adestination address of the first data packet; and sending, by the sourcedata node, the first data packet to a corresponding source control nodeto enable the source control node to determine a destination controlnode according to the destination address of the first data packet, andthe destination control node generates a second data packet according tothe first data packet.
 14. The data processing method according to claim13, wherein, the second data packet includes a destination address ofthe second data packet, and the method further comprises: receiving, bythe source data node, the second data packet sent by the destinationcontrol node; and sending, by the source control node, the second datapacket to a data node corresponding to the destination address of thesecond data packet.
 15. The data processing method according to claim13, wherein, the first data packet includes a source IP address of thefirst data packet, and before the sending, by the source data node, thefirst data packet to a corresponding source control node, the methodfurther comprises: determining the corresponding source control nodeaccording to the source IP address of the first data packet or accordingto mapping between the source data node and a control node.
 16. The dataprocessing method according to claim 13, wherein, the source data nodefurther stores a flow table, wherein the flow table is used to storesub-tuple information of a service flow data packet and a processingrule corresponding to the sub-tuple information; and after the sending,by the source data node, the first data packet to a corresponding sourcecontrol node, the method further comprises: receiving, by the sourcedata node, first control information sent by the destination controlnode; and adding, by the source data node, according to the firstcontrol information, a control node number field and a service parameterfield in the flow table of the source data node, wherein the controlnode number field represents an index of a destination control nodecorresponding to the source data node, and the service parameter fieldrepresents an index corresponding to a processing result of thesub-tuple information of the service flow data packet.
 17. The dataprocessing method according to claim 16, wherein, after adding thecontrol node number field and the service parameter field in the flowtable of the source data node, the method further comprises: receiving,by the source data node, a third data packet, wherein both the thirddata packet and the first data packet belong to the service flow datapacket, and a processing rule corresponding to sub-tuple information ofthe third data packet is the same as the processing rule correspondingto the sub-tuple information of the first data packet; determining, bythe source data node according to the flow table, a service parametercorresponding to the sub-tuple information from a processing rule recordmatching the sub-tuple information of the third data packet, wherein theservice parameter represents an index of an action parameter or a policyparameter to be executed for the third data packet; and carrying, by thesource data node, the service parameter in the third data packet andsending the third data packet to the destination control node, to enablethe destination control node to determine, according to the serviceparameter and the application layer information of the third datapacket, the action parameter or policy parameter executed for the thirddata packet, so as to generate a fourth data packet.
 18. A softwaredefined network-based data processing method, comprising: receiving, bya destination control node, a first data packet, wherein the first datapacket includes a destination address of the first data packet, thedestination control node is determined by a source control nodeaccording to the destination address of the first data packet, and thesource control node corresponds to a source data node receiving thefirst data packet; and generating, by the destination control node, asecond data packet according to the first data packet and a matchingpolicy rule.
 19. The data processing method according to claim 18,wherein, before the receiving, by a destination control node, a firstdata packet, the method further comprises: receiving, by the destinationcontrol node, a fifth data packet sent by the source control node,wherein the fifth data packet includes a destination address of thefifth data packet; determining a destination data node according to thedestination address of the fifth data packet; and if the destinationcontrol node does not manage the destination data node, determining afirst control node managing the destination data node and the sourcedata node as a second destination control node.
 20. The data processingmethod according to claim 18, wherein, the receiving, by a destinationcontrol node, a first data packet comprises: receiving, by thedestination control node, the first data packet sent by the sourcecontrol node or the source data node.
 21. The data processing methodaccording to claim 18, wherein, the matching policy rule comprises:mapping/correspondence between sub-tuple information and an actionparameter or a policy parameter, or mapping between application layerinformation and an action parameter or a policy parameter; and thegenerating, by the destination control node, a second data packetaccording to the first data packet and a matching policy rule comprises:searching the matching policy rule, according to sub-tuple informationof the first data packet or application layer information of the firstdata packet, for an action parameter or a policy parameter correspondingto the sub-tuple information of the first data packet or the applicationlayer information of the first data packet; and generating the seconddata packet according to the found action parameter or policy parameter.22. The data processing method according to claim 18, wherein, thematching policy rule comprises: mapping/correspondence between sub-tupleinformation and an action parameter or a policy parameter, or mappingbetween application layer information and an action parameter or apolicy parameter; and the generating, by the destination control node, asecond data packet according to the first data packet and a matchingpolicy rule comprises: searching the matching policy rule, according tosub-tuple information of the first data packet or application layerinformation of the first data packet, for an action parameter or apolicy parameter corresponding to the sub-tuple information of the firstdata packet or the application layer information of the first datapacket; sending, according to the found action parameter or policyparameter, capability request information to a first serving node havingthe capability of executing the action parameter or policy parameter inone or more serving nodes; receiving, by the destination control node,corresponding capability response information sent by the first servingnode in response to the capability request information; and generating,by the destination control node, the second data packet according to thecapability response information.
 23. The data processing methodaccording to claim 18, wherein, after the determining, by the sourcecontrol node, a destination control node according to the destinationaddress of the first data packet, the method further comprises: sending,by the destination control node, first control information to the sourcedata node, wherein the first control information is used to add acontrol node number field and a service parameter field in a flow tableof the source data node, the control node number field represents anindex of a destination control node corresponding to the source datanode, and the service parameter field represents an index correspondingto a processing result of sub-tuple information of the service flow datapacket.
 24. The data processing method according to claim 23, wherein,after adding the control node number field and the service parameterfield in the flow table of the source data node, the method furthercomprises: receiving, by the destination control node, a third datapacket including a service parameter, wherein both the third data packetand the first data packet belong to the service flow data packet, aprocessing rule corresponding to sub-tuple information of the third datapacket is the same as the processing rule corresponding to the sub-tupleinformation of the first data packet, the service parameter is a serviceparameter corresponding to the sub-tuple information, which isdetermined from a processing rule record matching the sub-tupleinformation of the third data packet, and the service parameterrepresents an index of an action parameter or a policy parameter to beexecuted for the third data packet; determining, by the destinationcontrol node according to the service parameter and application layerinformation of the third data packet, the action parameter or policyparameter executed for the third data packet, so as to generate a fourthdata packet; and sending, by the destination control node, the fourthdata packet to the source data node.
 25. A data node for softwaredefined network-based data processing, comprising: a first receivingmodule and a first sending module, the first receiving module beingconnected to the first sending module, wherein: the first receivingmodule is configured to receive a first data packet; and the firstsending module is configured to send the first data packet received bythe first receiving module to a corresponding source control node, toenable the source control node to determine a destination control nodeaccording to a destination address of the first data packet, and thedestination control node generates a second data packet according to thefirst data packet.
 26. The data node according to claim 25, wherein, thefirst receiving module is further configured to receive the second datapacket sent by the destination control node; the first sending module isfurther configured to send, according to a destination address of thesecond data packet carried in the second data packet, the second datapacket received by the receiving module to a data node corresponding tothe destination address.
 27. The data node according to claim 25,further comprising: a storage module, wherein the storage module isconfigured to store a flow table, the flow table is used to storesub-tuple information of a service flow data packet and a processingrule corresponding to the sub-tuple information.
 28. The data nodeaccording to claim 27, further comprising: a first processing module,wherein the first processing module is connected to the first receivingmodule; the first receiving module is further configured to receivefirst control information sent by the destination control node; and thefirst processing module is configured to add, according to the firstcontrol information, a control node number field and a service parameterfield in the flow table of the storage module, wherein the control nodenumber field represents an index of a destination control nodecorresponding to the source data node, and the service parameter fieldrepresents an index corresponding to a processing result of thesub-tuple information of the service flow data packet.
 29. The data nodeaccording to claim 28, wherein, the first processing module is connectedto the first sending module, the first receiving module is furtherconfigured to receive a third data packet, wherein both the third datapacket and the first data packet belong to the service flow data packet,and a processing rule corresponding to sub-tuple information of thethird data packet is the same as the processing rule corresponding tothe sub-tuple information of the first data packet; the first processingmodule is further configured to determine, according to the flow table,a service parameter corresponding to the sub-tuple information from aprocessing rule record matching the sub-tuple information of the thirddata packet, wherein the service parameter represents an index of anaction parameter or a policy parameter to be executed for the third datapacket; and the first sending module is further configured to carry theservice parameter in the third data packet and sends the third datapacket to the destination control node, to enable the destinationcontrol node to determine, according to the service parameter andapplication layer information of the third data packet, the actionparameter or policy parameter executed for the third data packet, so asto generate a fourth data packet.
 30. A destination control node forsoftware defined network-based data processing, comprising: a secondreceiving module, configured to receive a first data packet, wherein thefirst data packet includes a destination address of the first datapacket, the destination control node is determined by a source controlnode according to the destination address of the first data packet, andthe source control node corresponds to a source data node receiving thefirst data packet; and a second processing module, configured togenerate a second data packet according to the second data packetreceived by the second receiving module and a matching policy rule. 31.The control node for data processing according to claim 30, wherein: thesecond receiving module is further configured to receive a fifth datapacket, wherein the fifth data packet includes a destination address ofthe fifth data packet; and the second processing module is configured todetermine a destination data node according to the destination addressof the fifth data packet; and if the second processing module does notmanage the destination data node, determine a first control nodemanaging the destination data node and the source data node as a seconddestination control node.
 32. The control node for data processingaccording to claim 30, wherein, the second receiving module isconfigured to receive the first data packet sent by the source controlnode or the source data node.
 33. The control node according to claim30, wherein, the matching policy rule comprises: mapping/correspondencebetween sub-tuple information and an action parameter or a policyparameter, or mapping between application layer information and anaction parameter or a policy parameter; and the second processing modulecomprises: a policy matching unit, configured to search the matchingpolicy rule, according to sub-tuple information of the first data packetor application layer information of the first data packet, for an actionparameter or a policy parameter corresponding to the sub-tupleinformation of the first data packet or the application layerinformation of the first data packet; and a second data packetgenerating unit, configured to generate the second data packet accordingto the action parameter or policy parameter found by the policy matchingunit.
 34. The control node according to claim 30, wherein, the matchingpolicy rule comprises: mapping/correspondence between sub-tupleinformation and an action parameter or a policy parameter, or mappingbetween application layer information and an action parameter or apolicy parameter; the second processing module comprises: a policymatching unit and a second data packet generating unit, wherein thepolicy matching unit is configured to search the matching policy rule,according to sub-tuple information of the first data packet orapplication layer information of the first data packet, for an actionparameter or a policy parameter corresponding to the sub-tupleinformation of the first data packet or the application layerinformation of the first data packet; the second sending module isfurther configured to send, according to the action parameter or policyparameter found by the policy matching unit, capability requestinformation to a first serving node having the capability of executingthe action parameter or policy parameter in one or more serving nodes;the second receiving module is further configured to receivecorresponding capability response information sent by the first servingnode in response to the capability request information; and the seconddata packet generating unit is configured to generate the second datapacket according to the capability response information received by thesecond receiving module.
 35. The control node according to claim 30,wherein, the second sending module is further configured to send firstcontrol information, wherein the first control information is used toadd a control node number field and a service parameter field in a flowtable of the source data node, the control node number field representsan index of a destination control node corresponding to the source datanode, and the service parameter field represents an index correspondingto a processing result of sub-tuple information of the service flow datapacket.
 36. The control node according to claim 35, wherein: the secondreceiving module is further configured to receive a third data packetcarrying a service parameter, wherein both the third data packet and thefirst data packet belong to the service flow data packet, a processingrule corresponding to sub-tuple information of the third data packet isthe same as the processing rule corresponding to the sub-tupleinformation of the first data packet, the service parameter is a serviceparameter corresponding to the sub-tuple information, which isdetermined from a processing rule record matching the sub-tupleinformation of the third data packet, and the service parameterrepresents an index of an action parameter or a policy parameter to beexecuted for the third data packet; the second processing module isfurther configured to determine, according to the service parameter andapplication layer information of the third data packet, the actionparameter or policy parameter executed for the third data packet, andgenerate a fourth data packet; and the second sending module is furtherconfigured to send the fourth data packet to the source data node.